-
Notifications
You must be signed in to change notification settings - Fork 132
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
Investigate 6.0 SDK missing file: shared/Microsoft.NETCore.App/6.0.0/.version
#2569
Comments
It is used here: I actually have it in my local build:
Maybe it is hidden because it starts with a UPDATE: Oops - I was looking in the |
I can't find anyone who uses the shared fx That said, I agree we should have the same files as the Microsoft build. |
The <ItemGroup>
<!-- Work around issue where local clone may cause failure using non-origin remote fallback: https://github.com/dotnet/sourcelink/issues/629 -->
<InnerBuildEnv Include="EnableSourceControlManagerQueries=false" />
<InnerBuildEnv Include="EnableSourceLink=false" />
<InnerBuildEnv Include="DisableSourceLink=true" />
<InnerBuildEnv Include="DeterministicSourcePaths=false" />
</ItemGroup> Re-enabling sourcelink is tracked in source-build: In theory, the underlying bug (dotnet/sourcelink#629) can be treated as just a missing dev scenario--you are unable to use custom remote names while running ArPow. It could be ignored and sourcelink turned back on in dotnet/runtime. I've submitted dotnet/installer#12527 to give it a try. @dotnet/source-build-internal @omajid, thoughts on the dev scenario, if it's worthwhile to take this as a 6.0.0 patch if it doesn't regress anything? |
Note, the Fedora 34 5.0 SDK does contain this |
@jkoritzinsky - is there a reason that the <Target Name="_CreateVersionsFile"
DependsOnTargets="InitializeSourceControlInformationFromSourceControlManager"
Condition="'$(DisableSourceLink)' != 'true'"> |
That was ported over from the initial infrastructure that @dagood implemented in 3.1. I believe it's disabled because the |
I think it'd be reasonable to change the condition/targets to remove But ideally sourcelink could just be enabled, to avoid special-casing it. Normally, it seems pretty reasonable to assume that if sourcelink isn't available, the commit hash (if any) isn't discoverable. |
We're planning on leaving this diff in the 6.0.100 source-built SDK and not adding a patch yet. (dotnet/installer#12527.) This will help 6.0.100 stability. We've done smoke-testing and manual validation on what we have now, and haven't found any issues with leaving this file out. Seems like we can add a fix in 6.0.101/next servicing release. |
Closing as a patch was added in source-build and was backported to runtime. |
In the Microsoft-built SDK, this file contains the commit hash on the first line and then the version number on a second line. I don't think anyone uses it (it's just informational) but it would be good to fix this diff if it's a small thing.
dagood#9 (comment)
The text was updated successfully, but these errors were encountered: