NativeAOT Flag

[AathifMahir]

It would be great, if the Package Author does have option to Mark Packages as NativeAOT Compatible. that would Add Flag on Nuget Home, Where Devs can easily Identify if the Package does Support NativeAOT by Looking Into the Flags that Next Supported Dotnet like Below Image

[ghost]

Issue is missing Type label, remember to add a Type label

[nkolev92]

@AathifMahir I don't think NativeIOT is something known to NuGet, or something expressed in the package.

How would we recognize these special packages/

[AathifMahir]

@AathifMahir I don't think NativeIOT is something known to NuGet, or something expressed in the package.

How would we recognize these special packages/

That's where PublishAOT comes in, when a package does contains PublishAOT on it's csproj. The nuget adds NativeAOT flag, That's it simple

[nkolev92]

Ah, I see. In that case you can use a tag for that. https://learn.microsoft.com/en-us/nuget/reference/nuspec#tags, PackageTags is the msbuild equivalent: https://learn.microsoft.com/en-us/nuget/reference/msbuild-targets#pack-target.

[AathifMahir]

Ah, I see. In that case you can use a tag for that. https://learn.microsoft.com/en-us/nuget/reference/nuspec#tags, PackageTags is the msbuild equivalent: https://learn.microsoft.com/en-us/nuget/reference/msbuild-targets#pack-target.

I know we can use tags but having a special NativeAOT next Supported Dotnet is really going help lots of devs in my opinion over Traditional Tags, Since NativeAOT is main theme of Dotnet going forward. It totally make sense to have it next Supported Dotnet version as a Tag.

[nkolev92]

I'm moving the issue back to Home, since I had misread the original issue, but I think we'd to hear feedback around this topic.

It's worth nothing that NuGet does not really recognize assembly specific behavior, but rather focuses on compatible with frameworks and rids as pivots.