-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Template does not show up after install #11
Comments
Could you let us know whether or not the other templates from ASP.NET Core Template Pack are appearing? Is it just the Angular one that's not appearing for you, or the others too (e.g., Vue.js with Webpack)? |
The only templates I see under Installed->Templates->Visual C#->Web are ASP.Net Web Application (.Net Framework), ASP.Net Core Web Application( .Net Core) and ASP.Net Core Web Application( .Net Framework) |
Thanks for clarifying. In that case, I think this is one for @madskristensen because it implies an issue with installing any of the templates in this pack, rather than just the Angular one specifically. |
At first I thought i saw no new templates, but I was looking under ".Net Core" instead of "Web". |
Installed product versions
Windows Version
After installing pre-requsites non-of the templates from the pack are avaiable in the File->New Project. |
@jimpevans For me, at first the template didn't show up, but I changed the new project target framework to .Net Framework 4.6 and it showed up. |
@diegomesata I tried the tip you gave to @jimpevans and the templates are there. Thanks! |
Followed instructions in this article http://blog.stevensanderson.com/2016/10/04/angular2-template-for-visual-studio/ and verified that all prereq's were installed first - restarted not only VS but machine and still the template does not show up ion VS
Installed product versions
Description
Template does not show up after install
Steps to recreate
Current behavior
The template does not show up and is not accessible
Expected behavior
Template should show up
The text was updated successfully, but these errors were encountered: