Targeting net20 results in broken reference warnings

[davkean]

From @jnm2 on December 17, 2016 17:54

(I'm multitargeting net20 and netstandard1.3 but this happens also when just targeting net20.)

Under Dependencies > Assemblies I have System, System.Core, System.Data, System.Drawing, System.Runtime.Serialization, System.Xml and System.Xml.Linq. Of these I only actually need System, so ordinarily I'd delete the rest. However deleting is impossible since they are defined outside my .csproj.

Not being able to delete doesn't bother me too much, except that I get build warnings for System.Core, System.Runtime.Serialization and System.Xml.Linq due to targeting net20.

If you are going to require mandatory assembly references if one of the targets is .NET Framework, I'd expect you to detect which references make sense to add given the framework version. (Personally I'd be even more happy with no mandatory references and having to list them in the .csproj so I can delete all of them except System.)

Copied from original issue: dotnet/project-system#987

[nguerrera]

@dsplaisted #379 does not account for assemblies that are not in 2.0.

@jnm2 You can add the following to your project and then control the references yourself:

<PropertyGoup>
  <DisableImplicitFrameworkReferences>true</DisableImplicitFrameworkReferences>
</PropertyGroup>

[davidfowl]

We should fix that. The older CLI had that logic:

https://github.com/dotnet/cli/blob/v1.0.0-preview2.1/src/Microsoft.DotNet.ProjectModel/Resolution/ProjectDependencyProvider.cs#L52-L65

[nguerrera]

Yes, we should.