I've installed Visual Studio 15.
When I want to add new project, the ASP.NET Core Web Application (.NET Core) does not exist in project templates.
I've installed .NET Core and I'm using it on VS 2015.
Tooling for .NET core is not available in VS15 yet. https://www.visualstudio.com/en-us/news/releasenotes/vs15-relnotes
Visual Studio Tools for .NET Core availability
Issue:
Tooling support for .NET Core projects is not available in this
release of Visual Studio.
Workaround:
Support will be available in a future update of Visual Studio “15”.
It is due to the .Net Core Tool which is yet not released for VS2015. So if you want to use it then you have to go for VS2017.
Related
Currently I am using Visual studio 2017 and it that asp.net core. In that there is showing version asp.net core 2.1.
But this is not the latest version for using asp.net core 2.1. So how can I want to use in asp.net core 2.2 in existing visual studio, which is 2017
Shorten Answer:
Suggest you using official website to download ASP.NET Core SDKs and then run the downloaded file to install the SDK. Relaunch the Visual Studio and create a Web Application and then you'll find the ASP.NET Core 2.2.
From the release notes said Visual Studio 2017 support sdk version is end with SDK 2.2.106. Begin with SDK 2.2.203, you need use Visual Studio 2019 version 16.0. So Visual Studio 2017 does not support the latest version of ASP.NET Core 2.2. The latest version that Visual Studio 2017 can download is 2.2.106(Runtime version is 2.2.4).
Besides, the official document does not emphasize the Visual Studio 2017 specific version, it is better to use the latest version. Because if the Visual Stuidio version does not match the SDK version, it will not display ASP.NET Core 2.2 when you create a web application.
For example:
For my 64-bit version of Windows, I will choose the following link to download the sdk:
Note:
ASP.NET Core current release version is .NET 7 preview 1, ASP.NET Core 2.2 is actually an old version.
I instaled Visual Studio 2019 and updated Visual studio to Version 16.4.5. I have
the component "Microsoft .NET Core SDK 3.1.101 (x64) from Visual Studio" installed in my PC. But when a try to create a web application in Core 3.1, I dont get the web templates. I have only the ones shown in the picture. I would appreciate some help on how to have the templates when creating a Core project
The project templates were available when I downloaded the 3.1 SDK from link
i am trying to learn .net core with VS 2017. i dont have any basic idea about .NET Core development. Can any one suggest how can i start my first sample development in Visual Studio 2017?
To start with ASP.NET core, you must have visual studio 2017 installed and download the .Net Core SDK from: https://dotnet.microsoft.com/download/dotnet-core. I recommend that you download version 2.2 for VS 2017.
And have the web development package installed through Visual Studio Installer.
But, it would be better if you already started your studies with the VS 2019.following the same steps above.
VS 2019 already comes with SDKS for .Net core development
Can I work in my ASP.NET Core 2.1 Preview 1 project in Visual Studio 2017 (15.6.3) which is released today? https://learn.microsoft.com/en-us/visualstudio/releasenotes/vs2017-relnotes#15.6.3
I've been using Visual Studio 2017 Preview version to work on my ASP.NET Core 2.1 project up until now -- as this article suggests: https://blogs.msdn.microsoft.com/dotnet/2018/02/27/announcing-net-core-2-1-preview-1/
I want to know if I can switch back to the stable version of Visual Studio 2017 now.
When launching a solution that contains a .NET Core 2.1 project with Visual Studio 15.6.3, there will be the following message:
The link there goes to this page:
.NET Core 2.1 Preview 1
To create or open applications targeting .NET Core 2.1, Visual Studio 2017 15.7 or newer is recommended. Right now 15.7 is only available as a preview, so please use the latest Visual Studio 2017 Preview.
Visual Studio 2017 15.6 supports creating and opening applications targeting .NET Core 2.1, but it contains known issues so 15.7 or newer is recommended.
Visual Studio 2017 15.5 does not support creating or opening applications targeting .NET Core 2.1.
So you can absolutely use VS 15.6 for .NET Core 2.1 projects. In fact, just today I was working on a .NET Core 2.1 project (actually using a daily build), and I did not encounter any issues with my non-preview Visual Studio.
But there may be issues, e.g. with tooling related to scaffolding, so you should be prepared that things might break. But for normal work on an existing code base, there shouldn’t actually be any problems. And you could always fall back to the dotnet CLI for the things that don’t work.
tl;dr With the 15.6.3 update, there is still no official support for .NET Core 2.1 projects but there may be very few issues that will prevent you from actually working with it.
Now that ASP.NET Core is shipped with VS 2017(getting released on March), How long will they support ASP.NET Core in VS 2015?
I mean project.json will no longer be used, then do we need to move existing projects to VS 2017 and dont use VS 2015 to work with ASP.NET Core.
Visual Studio 2015 will only support .NET Core <= 1.1 (ie. project.json). If you wish to use .csproj based .NET Core projects you will need to use Visual Studio 2017. You can read about the .NET Core Roadmap here.
You can stick with project.json and Visual Studio 2015. But if you want to move to .NET Core 2.0 you will need to open your project with Visual Studio 2017 which can migrate it to the new .csproj format. You can read about the migration process in this blog post.
Visual Studio 2017 will also provide stable RTM tooling for .NET Core 1.0 (note that the tooling in Visual Studio 2015 is only in preview). There is another interesting blog post here which discusses the move to the new project format, Joe Morris from Microsoft confirms there are no plans to have VS 2015 support the build/project system.
Update
With the release of Visual Studio 2019, the latest .NET Core SDKs are not supported in Visual Studio 2015 or 2017. Here is the compatibility matrix: