![]() ![]() \src\MyWebAPI” (my project is called “MyWebAPI”, yours will be different), and then I type “ dotnet build“to compile the project. Finally, I change directory into my project by typing “cd.Next, I type “dotnet restore” (I think that this step is technically not necessary, but I like to do it to be sure I have updated the entire solution).Next I type “Update-Package” to get the latest NuGet packages for the v1.1 configuration.I open a PowerShell prompt (by going to Tools -> NuGet Package Manager -> Package Manager Console) – first I check my present working directory is at the root of my solution by typing “pwd”.To do this, we need to update NuGet packages, but fortunately this is easy. We’re not done yet – whereas if we build the projects we’ll see that version 1.1 is being targeted, but we’re not going to see many changes from 1.1 until we update the APIs available to us. However, if I open the global.json file for this project, we can see it does not target. Immediately after creating the project, VS2015 alerted me that it was restoring packages, and it completed this successfully. VS2015 doesn’t specify the target version at the time of project creation. I opened Visual Studio 2015 and created a new Web API project targeting. NET Core 1.1 SDK has a folder that doesn’t actually contain the version number “1.1” – it’s still marked as “1.0.0”, but it at least has the sub-version of 3177 present at the end of the folder name. NET Core which can happily exist side by side. You can see I’ve also installed a couple of other previous versions of. NET Core SDK (v 1.1), there was a new SDK folder on my hard disk at C:\Program Files\dotnet\sdk, as shown below. The file is called: DotNetCore.1.0.1-VS2015Tools.Preview2.0.3.exe – so unfortunately you can see it’s still marked as version 1.0.1.NET Core 1.1 for Visual Studio 2015 from here. I’ve also installed the tools (Preview 2) for.I’ve found this a bit confusing, so I wanted to post my findings and workarounds in case anyone else was struggling too.Īs is the case with a few of my posts – which cover preview technologies – I hope this information becomes obsolete soon, as new and more stable packages are released. There are a few gotchas – I think Microsoft understand that the numbering conventions need some work, and I’d expect these to be sorted out soon. NET Core – and creating my new projects with Visual Studio 2015. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |