Przemyslav
Reputation: 1
Referencing legacy .NET project in newer framework and with package version discrepancies
I need to setup an ASP.NET Core Web API and reference in it my other project which is written to run on .NET 4.6.1 (and it is using Entity Framework Core 3.6.1).
I found this article saying that to reference a .NET Framework 4.6.1 Assembly I need to use .NET Core 2.0. So using it and starting new project netcoreapp2.0 I am referencing to Microsoft.AspNetCore.All v2.0.9 which is referencing to Entity Framework Core v2.0.3. And this makes my old assembly incompatible with the new one. At least the I get such notifications when I am to build new project.
Is there a proper way to reference such a legacy assembly?
I have already tried:
- to decrease version of .NET Framework assembly
- increase version of
Microsoft.AspNetCore.Allin new project - changing reference to
Microsoft.AspNetCoreandMicrosoft.AspNetCore.Appin new project - adding reference to Entity Framework Core v3.6.1
Upvotes: 0
Views: 52
Answers (0)
Related Questions
- What is the difference between .NET Core and .NET Standard Class Library project types?
- Why do I get a warning icon when I add a reference to an MEF plugin project?
- Download old version of package with NuGet
- You must add a reference to assembly 'netstandard, Version=2.0.0.0
- Use .NET Core with legacy .NET framework dlls
- How do I reference a .NET Framework project in a .NET Core project?
- .net Core 2.0 - Package was restored using .NetFramework 4.6.1 instead of target framework .netCore 2.0. The package may not be fully compatible
- What 'additional configuration' is necessary to reference a .NET 2.0 mixed mode assembly in a .NET 4.0 project?
- .NET Framework 4.6.2 and .NET Standard 2.0 incompatibility
- Referencing .NET Standard csproj project from .NET Framework traditional project