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
Anders Laub's VsTemplates VS extension supports project-local templates by placing a .helixtemplates in the same folder as the solution file. It can then specify a relative folder (eg. HelixTemplates) that contain the Visual Studio templates and they'll automatically appear if you create a new project using the "Helix Project" template.
What do you think about including some templates for foundation/feature/project? It would be entirely optional by the user; the folder would be ignored if they don't have/use the Helix.VsTemplates extension.
Beyond the templates + manifests, here's what we'd need in the .helixtemplates file:
This would be awesome to have some preconfigured properties on certain file types. We often see that developers misconfigure build and copy properties which can cause problems, such as deploying web.configs and breaking upstream environments.
@marcelgruber Good point, though for your specific example setting Web.config to None isn't necessary as as WPP only includes the Web.config from the Website project
Anders Laub's VsTemplates VS extension supports project-local templates by placing a
.helixtemplates
in the same folder as the solution file. It can then specify a relative folder (eg. HelixTemplates) that contain the Visual Studio templates and they'll automatically appear if you create a new project using the "Helix Project" template.What do you think about including some templates for foundation/feature/project? It would be entirely optional by the user; the folder would be ignored if they don't have/use the Helix.VsTemplates extension.
Beyond the templates + manifests, here's what we'd need in the
.helixtemplates
file:The text was updated successfully, but these errors were encountered: