You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 15, 2020. It is now read-only.
Reporting an idea I got by email from one of the users:
Yeoman generatorIt would give you a few benefits over the current version:
It would be an npm package that could be downloaded and run via the 'yo' command for anyone who uses Yeoman, instead of being cloned directly from Github.
Changes and versioning could be handled in a more standard way.
Project names would be generated by the user rather than changed manually after cloning the repository.
Any guids for the server side will be randomly generated, eliminating potential issues that arise if someone uses multiple versions of your project with the same guid within a Visual Studio solution (for instance, if they copied the server project to act as an API in their DMZ to act as a pass through to an internal API).
The text was updated successfully, but these errors were encountered:
Reporting an idea I got by email from one of the users:
Yeoman generatorIt would give you a few benefits over the current version:
It would be an npm package that could be downloaded and run via the 'yo' command for anyone who uses Yeoman, instead of being cloned directly from Github.
Changes and versioning could be handled in a more standard way.
Project names would be generated by the user rather than changed manually after cloning the repository.
Any guids for the server side will be randomly generated, eliminating potential issues that arise if someone uses multiple versions of your project with the same guid within a Visual Studio solution (for instance, if they copied the server project to act as an API in their DMZ to act as a pass through to an internal API).
The text was updated successfully, but these errors were encountered: