You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The new .NET 8 assemblies are still being packages with .nuspec files instead of letting SDK-style project files do the work. Those .nuspac files have not been updated, so natively-compiled .NET 8 assemblies are being incorrectly delivered into .netstandard2.0 folders in the NuGet package.
Assemblies affected
ODL 8.x
Reproduce steps
Open the Microsoft.Data.Edm.csproj file and see that it targets .NET 8.0 exclusively.
Open the NuSpec file and see that the .NET 8 assembly is incorrectly packaged into the .NET Standard 2.0 folder.
Expected result
The SDK-style projects would manage the different <TargetFrameworks> supported and add their compiled assets to the NuGet package appropriately.
Actual result
Features that are not supported by .NET Standard 2.0 are being compiled into incorrectly-constructed NuGet packages that may be causing issues downstream.
The text was updated successfully, but these errors were encountered:
robertmclaws
changed the title
ODL is being packages with the wrong framework
ODL is being packaged with the wrong framework
Oct 15, 2024
The new .NET 8 assemblies are still being packages with .nuspec files instead of letting SDK-style project files do the work. Those .nuspac files have not been updated, so natively-compiled .NET 8 assemblies are being incorrectly delivered into .netstandard2.0 folders in the NuGet package.
Assemblies affected
ODL 8.x
Reproduce steps
Expected result
The SDK-style projects would manage the different
<TargetFrameworks>
supported and add their compiled assets to the NuGet package appropriately.Actual result
Features that are not supported by .NET Standard 2.0 are being compiled into incorrectly-constructed NuGet packages that may be causing issues downstream.
The text was updated successfully, but these errors were encountered: