We're updating the issue view to help you get more done. 

NuGet package adds .NET Standard references even when adding the dependency as a full-framework reference

Description

Hello,

Remotion.Linq nuget package, version 2.1.1, pulls a bunch of .NET System nugets, even though that the target framework is not ".NET Standard" but .NET Framework 4.6.

These unnecessary references are collided with Postsharp reference resolver (the project would not compile, error message is attached at the bottom).

Can you please whether add a .NET Framework target in your nuget package, or simply remove the .NET Standard one (as it used to be until the latest release).

Thanks,
Miri

Error Message:
Unhandled exception (4.3.32.0, postsharp-net40-x86-srv.exe, CLR 4.0.30319.394806, Release): PostSharp.Sdk.CodeModel.BindingException: Ambiguous assembly binding policies: Assembly 'system.runtime, version=4.0.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a' redirects both to 'system.runtime, version=4.1.0.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a' and 'system.runtime, version=4.0.20.0, culture=neutral, publickeytoken=b03f5f7f11d50a3a'.
at PostSharp.Sdk.CodeModel.AssemblyBindingPolicyManager.EvaluatePolicy(IAssemblyName assemblyName, Boolean evaluateSystemPolicies)
at PostSharp.Sdk.CodeModel.CompareExtensions.^4+F3cylo(IAssemblyName _0, IAssemblyName _1, AssemblyBindingPolicyManager _2, BindingOptions _3, Boolean _4)
at PostSharp.Sdk.CodeModel.ModuleDeclaration.FindAssembly(IAssemblyName assemblyName, BindingOptions bindingOptions)
at PostSharp.Sdk.CodeModel.ModuleDeclaration.^nQbUijLO(String _0, IAssemblyName _1, BindingOptions _2)
at PostSharp.Sdk.CodeModel.ModuleDeclaration.FindType(Type reflectionType, BindingOptions bindingOptions)
at PostSharp.Sdk.CodeModel.DeclarationCache.^pFnf8wEt()
at PostSharp.Sdk.CodeModel.TypeRefDeclaration.get_TypeIdentifier()
at PostSharp.Sdk.CodeModel.CompareExtensions.DefinitionMatchesReference(INamedType definition, INamedType reference, BindingOptions options)
at PostSharp.Sdk.CodeModel.TypeRefDeclaration.^A9yFoe2uB3TC(ITypeSignature _0, BindingOptions _1)
at PostSharp.Sdk.CodeModel.TypeRefDeclaration.MatchesReference(ITypeSignature reference)
at PostSharp.Sdk.CodeModel.Collections.CustomAttributeDeclarationCollection.Contains(IType type)
at PostSharp.Sdk.Extensibility.Tasks.MulticastAttributeTask.^SgrhoGlQ(AssemblyRefDeclaration _0)
at PostSharp.Sdk.Extensibility.Tasks.MulticastAttributeTask.^+GwnKh4ZYHu3()
at PostSharp.Sdk.Extensibility.Tasks.MulticastAttributeTask.Execute()
at PostSharp.Sdk.Extensibility.Project.ExecutePhase(String phase)
at PostSharp.Sdk.Extensibility.Project.Execute()
at PostSharp.Hosting.PostSharpObject.ExecuteProjects()
at PostSharp.Hosting.PostSharpObject.InvokeProject(ProjectInvocation projectInvocation).

Activity

Show:
Michael Ketting
June 19, 2017, 6:01 AM

Yes, hopefully. I tried this weekend but there wasn't any time left before it was over :/

User known
June 19, 2017, 6:12 AM

Waiting forward.. 10x

User known
June 25, 2017, 12:16 PM

Hi Michael,

I wonder if there is a new corrected package...?
We use a 3rd party package that is dependent on Remotion.Linq.
We are really looking to the dependencies fix, so we can move on with our development.

Thanks a lot,
Miri

Michael Ketting
June 25, 2017, 8:20 PM


Hi Miri,
v2.1.2 is out now and from my own dependency tests things look good. Sorry, but I just couldn't squeeze it in any sooner :/
~Michael

User known
June 26, 2017, 7:02 AM

Excellent, this is working just as expected.
Thank you

Assignee

Michael Ketting

Reporter

User known

Labels

None

Time tracking

0m

Components

Fix versions

Affects versions

Priority

Normal
Configure