Skip to content
This repository was archived by the owner on Apr 8, 2020. It is now read-only.

Angular Template not downloading #1202

Closed
ILL35T opened this issue Aug 16, 2017 · 5 comments
Closed

Angular Template not downloading #1202

ILL35T opened this issue Aug 16, 2017 · 5 comments

Comments

@ILL35T
Copy link

ILL35T commented Aug 16, 2017

dotnet new --install Microsoft.AspNetCore.SpaTemplates::*
Downloads every template besides the angular one which is the one I need.
I tried uninstall and install via cmd. Didnt work.
vs2017temp

I am running:
VS2017: v15.3.0
NodeJS: v6.11.2
Windows 10 Home: v1703

@bbrandt
Copy link

bbrandt commented Aug 17, 2017

If you are able to update to ASP.NET 2.0 SDK, the Microsoft.AspNetCore.SpaTemplates are now included in the framework (#948), making the --install Microsoft.AspNetCore.SpaTemplates::* unnecessary. I can confirm that the angular template is available there.

image

@MiniverCheevy
Copy link

if they're not showing up (which they didn't for me) you can run

dotnet new --install Microsoft.DotNet.Web.Spa.ProjectTemplates::*

to install them. I didn't install the ASP.NET 2.0 SDK (which I didn't know existed), I installed the .NET Core 2.0 SDK

@bbrandt
Copy link

bbrandt commented Aug 17, 2017

@MiniverCheevy
I think your right, there's only a .NET Core 2.0 SDK. I was a bit confused by the different announcements for .NET Core 2.0 and ASP.NET Core 2.0 with different download links.

Why I had the templates already and you had to install them separately is a mystery to me.

@SteveSandersonMS
Copy link
Member

As you've discovered, angular/react/redux are now all in the .NET Core 2.0 SDK by default, and the others (aurelia/knockout/vue) are now in Microsoft.AspNetCore.SpaTemplates.

If you're upgrading from an older .NET Core SDK and had previously installed an older version of the SpaTemplates package then you could see older templates showing up. That might explain why @bbrandt already had them.

@ILL35T
Copy link
Author

ILL35T commented Sep 5, 2017

Thanks guys. Updating to Core 2.0 solved my issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants