- Debugging Dotnet Core Projects with Visual Studio Code Including Debugging Those Pesky Test Projects. Originally I was just going to do a quick write-up for debugging a test project, but I figured.
- Visual Studio for Mac; Visual Studio Code; Visual Studio Team Services; Visual Studio App Center; DevOps. Continuous Integration and Deployment; Git and Version Control. Today, we are releasing the.NET Core August 2018 Update. This update includes.NET Core 2.1.3 and.NET Core SDK 2.1.401.
- If you’re on Mac or Linux, or simply want a lightweight development option, you can use Visual Studio Code, Sublime, Atom, or your favorite text editor to write ASP.NET Core applications. When you install the.NET Core SDK on your machine, the dotnet command line tool is added to your PATH.
- .NET Core 2.0 is available today as a final release. You can start developing with it at the command line, in your favorite text editor, in Visual Studio 2017 15.3, Visual Studio Code or Visual Studio for Mac.
- Also released on Monday: Visual Studio 2017 version 15.3, which improves accessibility, particularly using Visual Studio with the most popular screen readers; and Visual Studio for Mac version 7.1, which adds support for.NET Core 2.0 targeting in console apps, web apps and web services.
Active4 months ago
Aug 14, 2017 You can start developing with it at the command line, in your favorite text editor, in Visual Studio 2017 15.3, Visual Studio Code or Visual Studio for Mac. It is ready for production workloads, on your own hardware or your favorite cloud, like Microsoft Azure.
Can i open a core 2.0 project in Visual Studio 2017?
I've installed the latest dotnet-core (2.0.0-preview2-005840) and created a core 2.0 console-app.
- Open console.csproj in Visual Studio 2017 with 'open project'
- Clean and Build Solutions
- i get several erros
- amongs others:
Unable to resolve 'Microsoft.NETCore.App (>= 2.0.0)' for '.NETCoreApp,Version=v2.0'.
So. Is it just not supported at the moment or am i missing something?
jens
![Core Core](https://developercommunity.visualstudio.com/storage/attachments/25896-screen-shot-2018-03-24-at-93038-am.png)
2,38244 gold badges2222 silver badges3232 bronze badges
4 Answers
Update:
There is now a VS 2017 15.3 preview that resolves this issue. Starting with VS 15.3, Visual Studio carries an MSBuild SDK resolver that determines which version of the CLI SDK a project would use (e.g. if a
global.json
sets the version) and uses it's MSBuild targets so new previews are picked up by VS.Updated Visual Studio For Mac No .net Core 2.org
Original:
You can modify your environment to get VS 2017 support for the unreleased 2.0 tooling by setting the
Martin UllrichMartin UllrichMSBuildSdksPath
as described in https://github.com/aspnet/Announcements/issues/231 so that VS picks up the build logic from the CLI.55k1111 gold badges149149 silver badges144144 bronze badges
The Visual Studio .NET Core tools were just released in March, yet the 2.0 preview you are using was released in April.https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/You'll need to wait for an update to the .NET Core Tools before you can use Visual Studio with .NET Core 2.0
NovaterataNovaterata
Visual Studio 2017 Version 15.3 Released and .NET Core 2.0 also Released with nuget v4.3 and the problem is resolved completely.
you can review all fixes Release notes
M.HassanM.Hassan4,75422 gold badges2727 silver badges4343 bronze badges
Landed on this today (April 2019) and it appears that now there is a version of .NET Core Tools SDK for VS 2017. Here's how you get to it:1. browse to http://dot.net2. Under .NET Core 2.2, look for 'Download .NET Core SDK (Compatible with Visual Studio 2017' 3. Visual studio 2017 (I have version 15.9.11) should now list .NET Core 2.2 as a target framework
Sudhanshu MishraSudhanshu Mishra4,24422 gold badges3939 silver badges6060 bronze badges