-
Notifications
You must be signed in to change notification settings - Fork 1.1k
GenerateAssemblyInfo is not ordered before BeforeCompile #10614
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
Comments
@tmat If the fix for this was merged into master, what SDK version does that mean it would arrive in? Does it need to be ported to any other branches? |
master is 5.0. If this is needed sooner than that, then this would need to be ported to 3.1.2xx to coincide with 16.5. That will require approval at this point. The 16.6 / 3.1.3xx would next opportunity, but branch does not exist yet. I imagine we could get this approved if you want to put up a port to release/3.1.2xx |
Reopening and targeting 3.1.2xx milestone for now. |
Yeah, I can port it to |
FYI, @wli3 Note that there is a possibility it will not be approved for 3.1.2xx, but then we can leave the PR open and retarget to 3.1.3xx when the branch opens. That is still much sooner than 5.0.1xx that master is targeting. |
PR for 3.1.2: #10616 |
#10616 was merged to 3.1.3xx. |
Does this mean that the fix landed in the official .NET Core 3.1.300 SDK? I just tried to |
FTR, given that NuGet packages exist which ship |
Answering myself: yes, the fix landed in the official .NET Core 3.1.300 SDK. My untracked sources issue was because the repository was missing a |
It is required for both MinVer and SourceLink to work properly. See adamralph/minver#347 and dotnet/sdk#10614
The common targets convention is to generate all source inputs to the compiler before BeforeCompile target.
Targets that fail to do so break Source Link (see dotnet/sourcelink#572).
The text was updated successfully, but these errors were encountered: