1.5.1 - Added target framework versions 4.7.1, 4.7.2 and 4.8

Added target framework versions 4.7.1, 4.7.2 and 4.8, can be used to create projects targeting .net frameworks higher than 4.7.

1.3.3 - .NET version options

Minor thing, but helpful for some!

Features

• Add option for .NET 4.6.2 for helix:add (#115 - Thanks @JaspervdM80 )

1.3.1 - Stores prompts & validates inputs and fixes a number of bugs

Minor version number change, but yet we indroduce features... how funny is that!!!!

Features

• Stores Prompt inputs (#89)
• Validate Project Name (#90)

Bugs

• Fix PowerShell Invoke Path (#94)

Other

• Updated dependencies to newest versions (#93)

1.3.0 - Support for Modules Groups

This release adds support for module groups, that's awesome and there were no bugs to fix. Enjoy.

Features

• Support for Modules Groups (#83)

1.2.0 - Features and fixes

This release fixes a number of bugs, while also providing a new feature! Awesome.

Features

• Automatically install dependencies when choosing solution with Pentia tools (#71) (thanks to @jimmah)

Bugs

• The environment project is located directly under the module folder (#63)
• PublishProfile should be added to the project (#41)
• Solution folder tests, is not compliant with helix structure. (#78)
• Local.pubxml is missing from Project.Environment (#79)

Support for vendor prefixes

This release adds support for vendor prefixes, with tests for this feature.

Features

• Vendor Prefixes (#70) (thanks to @saberone)

Bugs

None this time around!

Empty Solution add solution, CI, tests and guidelines

New features:
Empty solution now creates a solution.
CI added for github pull requests
Mocha tests added
Contributing.md added to help people with Contributing
Issue and pull request templates added.

Gulp dependency is now legit version

Gulp dependency is now legit version
Intake of PR #32 fixes faulty dependency to
non-existent version of gulp.

Scope: npm dependencies.

Create the targets declared in the solution file

v1.0.7

bump version

Handle spaces in NPM module location

The was an issue if the global location for NPM modules contained spaces.