-
Notifications
You must be signed in to change notification settings - Fork 4.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update product version to 6.0.0 #40950
Conversation
Anipik
commented
Aug 17, 2020
•
edited
Loading
edited
- update the package versions
- update the assembly and product verision
- fix the package baseline file using the repoupdatePackageBaseline target
- fix the paths.
Tagging subscribers to this area: @safern, @ViktorHofer |
Can you double check every project that
And add a |
@@ -12,8 +12,8 @@ | |||
// --- The following custom attribute is added automatically, do not uncomment ------- | |||
// .custom instance void [CORE_ASSEMBLY]System.Diagnostics.DebuggableAttribute::.ctor(valuetype [CORE_ASSEMBLY]System.Diagnostics.DebuggableAttribute/DebuggingModes) = ( 01 00 02 00 00 00 00 00 ) | |||
|
|||
.custom instance void [CORE_ASSEMBLY]System.Reflection.AssemblyFileVersionAttribute::.ctor(string) = ( 01 00 07 35 2E 30 2E 30 2E 30 00 00 ) // ...5.0.0.0.. | |||
.custom instance void [CORE_ASSEMBLY]System.Reflection.AssemblyInformationalVersionAttribute::.ctor(string) = ( 01 00 07 35 2E 30 2E 30 2E 30 00 00 ) // ...5.0.0.0.. | |||
.custom instance void [CORE_ASSEMBLY]System.Reflection.AssemblyFileVersionAttribute::.ctor(string) = ( 01 00 07 35 2E 30 2E 30 2E 30 00 00 ) // ...6.0.0.0.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought we had plumbed the correct data for this through the header?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we missed the hex strings
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i will hardcode for this pr and fix after the snap
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See #40895 we may want to fix for 5.0
Per offline conversation, this doesn't need to be done with the version change, but does need to happen when the TFM changes. The TFM change can be separate as it likely requires a bit more to make the SDK work with the new TFM. (EG: temporary KnownFrameworkReference) |
@@ -171,7 +173,8 @@ | |||
], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically we should be setting baselineVersion for all packages. However it's likely less important here since we don't ever use PackageReferences to the Microsoft.Extensions packages and none of their versions are frozen (so all assembly refs will be to 6.0.0.0 and thus get the 6.0.0-* packages).
eng/targetingpacks.targets
Outdated
@@ -2,7 +2,7 @@ | |||
<PropertyGroup Condition="'$(DisableImplicitFrameworkReferences)' != 'true' and | |||
'$(TargetFrameworkIdentifier)' == '.NETCoreApp' and | |||
$([MSBuild]::VersionGreaterThanOrEquals($(TargetFrameworkVersion), '$(NETCoreAppCurrentVersion)'))"> | |||
<_UseLocalTargetingRuntimePack>true</_UseLocalTargetingRuntimePack> | |||
<UseLocalTargetingRuntimePack Condition="'$(UseLocalTargetingRuntimePack)' == ''">true</UseLocalTargetingRuntimePack> | |||
<EnableTargetingPackDownload>false</EnableTargetingPackDownload> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we still want to download the targeting pack if UseLocalTargetingRuntimePack=false. It's possible that the SDK doesn't carry it (once it moves to net6.0
for example).
...aries/Microsoft.XmlSerializer.Generator/tests/Microsoft.XmlSerializer.Generator.Tests.csproj
Outdated
Show resolved
Hide resolved
<TargetFrameworks>$(NetCoreAppCurrent)</TargetFrameworks> | ||
<SkipTestsOnPlatform Condition="'$(TargetsMobile)' == 'true' or '$(TargetOS)' == 'FreeBSD' or '$(TargetArchitecture)' == 'arm' or '$(TargetArchitecture)' == 'arm64' or '$(TargetArchitecture)' == 'armel' or '$(TargetArchitecture)' == 'wasm'">true</SkipTestsOnPlatform> | ||
<UseLocalTargetingRuntimePack>false</UseLocalTargetingRuntimePack> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This deserves a comment. Let's mention that this test assembly needs to run on the tool shared framework so it should reference the latest references. We build against tool shared framework's ref pack, run the generator on the tool shared framework, then execute the test on the test shared framework.
...aries/Microsoft.XmlSerializer.Generator/tests/Microsoft.XmlSerializer.Generator.Tests.csproj
Outdated
Show resolved
Hide resolved
@@ -20,7 +20,7 @@ | |||
<SkipBaseLineCheck>true</SkipBaseLineCheck> | |||
|
|||
<!-- by default all packages will use the same version which revs with respect to product version --> | |||
<PackageVersion Condition="'$(PackageVersion)' == ''">5.0.0</PackageVersion> | |||
<PackageVersion Condition="'$(PackageVersion)' == ''">6.0.0</PackageVersion> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not for this PR, but we should try to make this use $(ProductVersion) if possible.