Solution a: I will change my frame core 3.0 to 2.2 obviously I'm not going to do this, this is my final way

Scheme 2: to upgrade to the core of 3.0 server environment, need your assessment under shock wave images already deployed in the project (I have a look at running project a dozen have seven or eight core2.2)

Solution 3: is there a way to make the core environment coexist core 2.2 is 3.0, the default 2.2 no effect on other projects, to specify my own projects as core can
3.0
Or is there still hope I didn't think of other ways

CodePudding user response:

On.net core deployment issues already exists on the server core2.2 environment (a project running) my project core 3.0 there are several solutions, please

CodePudding user response:

Installed on the server, 3.0

When the dotnet your program. DLL, dotnet (3.0) will choose installed, compatible, the latest, the patch version,
For example, if the netcoreapp2.0 specified in the project file, and 2.0.4 is to install the latest.net runtime, use the 2.0.4 runtime,

Detailed see:
] [choose to use the.net Core version of "rely on the framework application roll forward" section,
https://docs.microsoft.com/zh-cn/dotnet/core/versions/selection#framework-dependent-apps-roll-forward