Last post Mar 18, 2020 03:23 PM by bruce (sqlwork.com)
Mar 09, 2020 08:25 AM|jsshivalik|LINK
I have Visual Studio 2012. I want to develop Restful Api using token. Is there any tutorial or link available.
Can Api be developed in VS 2012 using Asp.net core.
Mar 09, 2020 02:21 PM|bruce (sqlwork.com)|LINK
just start with the asp.net core docs. This is all covered.
Vs2012 can not load asp.net core projects (file format not supported), nor compile or debug. But you could edit the source file. You’d be better off using visual studio code which is free.
Mar 10, 2020 07:05 AM|Sherry Chen|LINK
.NET Core 1.0, announced on November 12, 2014, was released on June 27, 2016, along with Microsoft Visual Studio 2015 Update 3, which enables .NET Core development. .NET Core 1.0.4 and .NET Core 1.1.1 were released along with .NET Core Tools 1.0 and Visual
Studio 2017 on March 7, 2017. For more details ,refer to
I want to develop Restful Api using token. Is there any tutorial or link available.
You could learn the below tutorial of how to implement JWT (JSON Web Token) authentication in an ASP.NET Core 3.1 API with C#.
Mar 18, 2020 10:20 AM|yogyogi|LINK
Can Api be developed in VS 2012 using Asp.net core. - NO
Don't use VS 2012 as it is very old. You should use VS 2019 community edition which is free and can be downloaded from Microsoft website.
You can start Rest API learning from the beginning from here.
Mar 18, 2020 03:23 PM|bruce (sqlwork.com)|LINK
telling people to upgrade VS often is not very useful. In many corporate environments you are not allowed to upgrade, and need to use the provided tools. if your company only allows VS 2012 you need to make do.
to use vs 2012 for .dotnet core the easiest to create a utility project. then add a subfolder that is the actually asp.net core project. use
dotnet new <option>
to create the project in this folder. you can edit the files with vs 2012, and even via custom tools do the build and publish. learn the dotnet cli as it has the scaffolding tools like add nuget or project reference. no debugging support unless you get a