Preference .NET Standard DLLs over Framework DLLs in Nuget package
up vote
0
down vote
favorite
I'm migrating my shared code from Framework to Standard. To keep things moving between our projects, we are currently maintaining both a full Framework version and a Standard version. The Framework codebase is only receiving critical updates while Standard is getting all the new dev.
Most of our APIs are still Framework. Until we can get them to Core, I'd like them to start referencing the Standard DLLs in our nuget package rather than the Framework. The nugets, currently, have both the Framework DLLs in them and the Standard DLLs.
My question is: is there a way to set, at the solution or project level, a preference so the DLL references try to use Standard first, then fallback to Framework?
nuget
asked Nov 9 at 14:02
Matt M
15111
add a comment |
up vote
0
down vote
favorite
I'm migrating my shared code from Framework to Standard. To keep things moving between our projects, we are currently maintaining both a full Framework version and a Standard version. The Framework codebase is only receiving critical updates while Standard is getting all the new dev.
Most of our APIs are still Framework. Until we can get them to Core, I'd like them to start referencing the Standard DLLs in our nuget package rather than the Framework. The nugets, currently, have both the Framework DLLs in them and the Standard DLLs.
My question is: is there a way to set, at the solution or project level, a preference so the DLL references try to use Standard first, then fallback to Framework?
nuget
asked Nov 9 at 14:02
Matt M
15111
1
This is not supported. NuGet will use the most specific target framework match it can find. If the project targets .NET Framework and the NuGet package has assemblies for .NET Framework, which are compatible, then they will be used. You could file an issue on github.com/nuget/home/issues to see what the NuGet team say about this.
– Matt Ward
Nov 10 at 22:22
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm migrating my shared code from Framework to Standard. To keep things moving between our projects, we are currently maintaining both a full Framework version and a Standard version. The Framework codebase is only receiving critical updates while Standard is getting all the new dev.
Most of our APIs are still Framework. Until we can get them to Core, I'd like them to start referencing the Standard DLLs in our nuget package rather than the Framework. The nugets, currently, have both the Framework DLLs in them and the Standard DLLs.
My question is: is there a way to set, at the solution or project level, a preference so the DLL references try to use Standard first, then fallback to Framework?
nuget
asked Nov 9 at 14:02
Matt M
15111
I'm migrating my shared code from Framework to Standard. To keep things moving between our projects, we are currently maintaining both a full Framework version and a Standard version. The Framework codebase is only receiving critical updates while Standard is getting all the new dev.
Most of our APIs are still Framework. Until we can get them to Core, I'd like them to start referencing the Standard DLLs in our nuget package rather than the Framework. The nugets, currently, have both the Framework DLLs in them and the Standard DLLs.
My question is: is there a way to set, at the solution or project level, a preference so the DLL references try to use Standard first, then fallback to Framework?
nuget
nuget
asked Nov 9 at 14:02
Matt M
15111
asked Nov 9 at 14:02
Matt M
15111
asked Nov 9 at 14:02
Matt M
15111
asked Nov 9 at 14:02
Matt M
15111
asked Nov 9 at 14:02
Matt M
15111
15111
1
This is not supported. NuGet will use the most specific target framework match it can find. If the project targets .NET Framework and the NuGet package has assemblies for .NET Framework, which are compatible, then they will be used. You could file an issue on github.com/nuget/home/issues to see what the NuGet team say about this.
– Matt Ward
Nov 10 at 22:22
add a comment |
1
This is not supported. NuGet will use the most specific target framework match it can find. If the project targets .NET Framework and the NuGet package has assemblies for .NET Framework, which are compatible, then they will be used. You could file an issue on github.com/nuget/home/issues to see what the NuGet team say about this.
– Matt Ward
Nov 10 at 22:22
1
1
This is not supported. NuGet will use the most specific target framework match it can find. If the project targets .NET Framework and the NuGet package has assemblies for .NET Framework, which are compatible, then they will be used. You could file an issue on github.com/nuget/home/issues to see what the NuGet team say about this.
– Matt Ward
Nov 10 at 22:22
This is not supported. NuGet will use the most specific target framework match it can find. If the project targets .NET Framework and the NuGet package has assemblies for .NET Framework, which are compatible, then they will be used. You could file an issue on github.com/nuget/home/issues to see what the NuGet team say about this.
– Matt Ward
Nov 10 at 22:22
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53227183%2fpreference-net-standard-dlls-over-framework-dlls-in-nuget-package%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
1
This is not supported. NuGet will use the most specific target framework match it can find. If the project targets .NET Framework and the NuGet package has assemblies for .NET Framework, which are compatible, then they will be used. You could file an issue on github.com/nuget/home/issues to see what the NuGet team say about this.
– Matt Ward
Nov 10 at 22:22