Skip to content
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

GenerateAssemblyInfo is not ordered before BeforeCompile #10614

Closed
tmat opened this issue Feb 7, 2020 · 11 comments · Fixed by #10613
Closed

GenerateAssemblyInfo is not ordered before BeforeCompile #10614

tmat opened this issue Feb 7, 2020 · 11 comments · Fixed by #10613
Assignees
Milestone

Comments

@tmat
Copy link
Member

tmat commented Feb 7, 2020

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).

@bording
Copy link

bording commented Feb 7, 2020

@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?

@tmat
Copy link
Member Author

tmat commented Feb 7, 2020

@nguerrera

@nguerrera
Copy link
Contributor

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

@nguerrera nguerrera reopened this Feb 7, 2020
@nguerrera nguerrera added this to the 3.1.2xx milestone Feb 7, 2020
@nguerrera
Copy link
Contributor

Reopening and targeting 3.1.2xx milestone for now.

@tmat
Copy link
Member Author

tmat commented Feb 7, 2020

Yeah, I can port it to release/3.1.2xx.

@nguerrera
Copy link
Contributor

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.

@tmat
Copy link
Member Author

tmat commented Feb 8, 2020

PR for 3.1.2: #10616

@rainersigwald
Copy link
Member

#10616 was merged to 3.1.3xx.

@0xced
Copy link

0xced commented May 26, 2020

#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 dotnet pack a project using the dotnet CLI version 3.1.300 but NuGet Package Explorer still reports that the package contains untracked sources. This is confusing. Also, this issue is in the 3.1.2xx milestone, adding even more confusion.

@adamralph
Copy link
Contributor

FTR, given that NuGet packages exist which ship .targets files which rely on the shape of the dependency graph, this is effectively a breaking change.

@0xced
Copy link

0xced commented Jun 2, 2020

Does this mean that the fix landed in the official .NET Core 3.1.300 SDK?

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 .gitignore file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants