Include IsNetCoreAppRef in assembly version calculation for servicing #65166
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is the long term fix for: #65018
This new pattern of experimental ref only projects where the implementation is inbox, needs to be considered as an assembly in the targeting pack, so we should not bump the assembly version on servicing, with this we make sure that we catch such cases and not bump the assembly version for these experimental ref only nuget packages.
The fix to release/6.0 will be ported as part of: #64556 as it is adding another ref only nuget package and needs to include it to unblock it's tests, however, we still need to have a PR created into release/6.0 to make sure we build
System.Runtime.Experimental
withServicingVersion
set to2
andGeneratePackageOnBuild
set totrue
.