Skip to content

Microsoft.NET.Test.Sdk: nupkg with TargetFramework=native0.0 #15366

@nicholi

Description

@nicholi

Since version 17.14.1 the published nupkg has an additional TFM defined as, targetFramework="native0.0". Which otherwise seems to be a TFM that does nothing, it has an empty lib/native directory.

Raising this issue primarily to find out if this TFM was intentionally added, or perhaps something that just got overlooked and should get removed or just otherwise not added when generating the .nuspec.

I am actually a user of paket, which is an alternative nuget client/package management tool. Whenever it installs the Microsoft.NET.Test.Sdk nupkg it also prints a warning about the unknown TFM.

$ dotnet paket install
Paket version 10.3.1+bbc45f336c7f9bac95cf1d17267ab2383d029682
Installing into projects:
Created dependency graph (# packages in total)
Could not detect any platforms from 'native0.0' in '/home/user/.nuget/packages/microsoft.net.test.sdk/17.14.1/microsoft.net.test.sdk.nuspec', please tell the package authors

Which is probably just comparing against all the older .NET Framework and .NET Core TFM names we've had over the years, but native0.0 isn't recognized as anything. Not an issue or any warning with the standard nuget client, likely just ignores it completely.

If this TFM is intended to be present, I expect this Issue to be closed. I will raise another Issue with Paket devs to see if native#.# should be recognized as a known platform. As Microsoft.NET.Test.Sdk is a pretty significant package to cite with a special TFM. Just looking to cut down on odd build warnings.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions