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
<DisplayVSMessageCondition="$([MSBuild]::VersionLessThan($(MSBuildVersion), '$(MinimumVisualStudioVersionForUnsupportedTargetFrameworkVersion)')) and '$(BuildingInsideVisualStudio)' == 'true' and '$(_TargetFrameworkVersionWithoutV)' == '$(UnsupportedTargetFrameworkVersion)' and '$([MSBuild]::IsOSPlatform(`Windows`))' == 'true'">true</DisplayVSMessage>
I'm not sure why we need the UnsupportedTargetFrameworkVersion property when we already have NETCoreAppMaximumVersion. The latter defines the maximum .NETCoreApp version that the SDK supports targeting. The former is basically NETCoreAppMaximumVersion+1.
This is now coming up because i.e. in runtime we target net10.0 with a .NET 9 SDK and set NETCoreAppMaximumVersion to 10.0. Now with the additional UnsupportedTargetFrameworkVersion property, we would also need to override that.
The text was updated successfully, but these errors were encountered:
sdk/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.TargetFrameworkInference.targets
Line 163 in d071d83
I'm not sure why we need the
UnsupportedTargetFrameworkVersion
property when we already haveNETCoreAppMaximumVersion
. The latter defines the maximum .NETCoreApp version that the SDK supports targeting. The former is basicallyNETCoreAppMaximumVersion
+1.This is now coming up because i.e. in runtime we target net10.0 with a .NET 9 SDK and set
NETCoreAppMaximumVersion
to 10.0. Now with the additionalUnsupportedTargetFrameworkVersion
property, we would also need to override that.The text was updated successfully, but these errors were encountered: