All geek questions in one place

ASP.Net Core 1.1 - Migration Error

I know that VS 2017 is only RC, but there seem to be some serious issues with porting the ASP.Net Core 1.0 project to 1.1. The migration tool could not convert 2 of my 8 projects into a solution (I prefer to use a multi-level architectural approach for my projects), a sample project is here . One project, in particular, is a class library to which I have moved the methods of the web api controller. When you try to recreate this class library, it is not possible to declare the controller class after installing Microsoft.AspNetCore.Mvc nuget. It is installed, but the compiler does not find the classes Controller, RouteAttribute, etc. The same problem occurred while trying to configure the DI level of IServiceCollection. Nuget Microsoft.Extensions.DependencyInjection does not seem to do this.

The migration journal, to be honest, doesn't really help me. This seems to indicate a problem with my project service and the project.json file, but as you can tell it is in the repository.

It seems that Microsoft is forcing us to iterate over all the “network” things into a single project file. Perhaps these instruments are not far enough away, but does the RC indicate that they should be closer to the ship's dispatch?

ReciPiBook.Api Message src \ ReciPiBook.Api \ ReciPiBook.Api.xproj: Failed to transfer the XProj ReciPiBook.Api project. "dotnet migrate -s -p" C: \ Users \ xxx \ Documents \ Visual Studio 2015 \ Projects \ ReciPiBook2017 \ ReciPiBookCore \ src \ ReciPiBook.Api "-x" C: \ Users \ xxx \ Documents \ Visual Studio 2015 \ Projects \ ReciPiBook2017 \ ReciPiBookCore \ src \ ReciPiBook.Api \ ReciPiBook.Api.xproj "" exited with error code 1. src \ ReciPiBook.Api \ ReciPiBook.Api.xproj: Could not find file 'C: \ Users \ xxx \ Documents \ Visual Studio 2015 \ Projects \ ReciPiBook2017 \ ReciPiBookCore \ src \ ReciPiBook.Services \ project.json '. Migration failed. src \ ReciPiBook.Api \ ReciPiBook.Api.xproj: Backup C: \ Users \ xxx \ Documents \ Visual Studio 2015 \ Projects \ ReciPiBook2017 \ ReciPiBookCore \ src \ ReciPiBook.Api \ ReciPiBook.Api.xproj for C: \ Users \ xxx \ Documents \ Visual Studio 2015 \ Projects \ ReciPiBook2017 \ ReciPiBookCore \ Backup \ src \ ReciPiBook.Api \ ReciPiBook.Api.xproj. src \ ReciPiBook.Api \ project.json: Backup C: \ Users \ xxx \ Documents \ Visual Studio 2015 \ Projects \ ReciPiBook2017 \ ReciPiBookCore \ src \ ReciPiBook.Api \ project.json for C: \ Users \ xxx \ Documents \ Visual Studio 2015 \ Projects \ ReciPiBook2017 \ ReciPiBookCore \ Backup \ src \ ReciPiBook.Api \ project.json.

+5
source share
1 answer

I can’t talk directly with VS2017, because I can’t refuse it, even if it is RC, the main tool is in ALPHA. The core of the VS 2015 tool is at least in the “RC” state (in fact, only a preview).

In VS2015, I moved from 1.0.x to 1.1 manually (for https://blogs.msdn.microsoft.com/dotnet/2016/11/16/announcing-net-core-1-1/ ):

  • Download 1.1 sdk
  • Change your global.json "sdk": {"version": "1.0.0-preview2-1-003177"} (yes, this is another version line).
  • Update all versions of project.json package from 1.0 to 1.1 (some of them are previews of some arn't). Just open the nuget package manager, enable pre-release versions and install all updates.
  • Correct any of your project.json tool entries as the package manager compresses them.
0
source

Source: https://habr.com/ru/post/1259873/

More articles:


All Articles