Issue #112 mentioned that the project guids are currently hard coded in the templates. This PR fixes that behavior by setting the assembly guid using the 'projectguid' variable already available.
To verify the guid is different per project you can run npm test and verify by checking the generated files.
Benefits
The project file that is generated now has a unique assembly guid and issue #112 can be closed 😄
Description of the Change
Issue #112 mentioned that the project guids are currently hard coded in the templates. This PR fixes that behavior by setting the assembly guid using the 'projectguid' variable already available.
To verify the guid is different per project you can run
npm testand verify by checking the generated files.Benefits
The project file that is generated now has a unique assembly guid and issue #112 can be closed 😄
Possible Drawbacks
None.