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

Source build fixes #67747

Merged
merged 6 commits into from
Apr 13, 2023
Merged

Source build fixes #67747

merged 6 commits into from
Apr 13, 2023

Conversation

jaredpar
Copy link
Member

The source build produced from our official build needs to include both the net7.0 and net8.0 packages. Those packages feed into the soucre build legs of other repos and they can be targeting either net7.0 or net8.0.

The source build produced from our official build needs to include both
the net7.0 and net8.0 packages. Those packages feed into the soucre
build legs of other repos and they can be targeting either net7.0 or
net8.0.
@jaredpar jaredpar requested a review from a team as a code owner April 11, 2023 18:48
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Issues and PRs which have not yet been triaged by a lead label Apr 11, 2023
@jaredpar
Copy link
Member Author

@dotnet/roslyn-compiler PTAL

@jaredpar jaredpar requested a review from a team as a code owner April 11, 2023 20:30
Jared Parsons added 2 commits April 11, 2023 13:50
Fix
Work around a bug in the public API analyzer

dotnet/roslyn-analyzers#6059
targeting NetCurrent or NetPrevious hence we must produce both.
- Source build the product: this is the all up build of the product which needs only NetCurrent
-->
<SourceBuildTargetFrameworks></SourceBuildTargetFrameworks>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit: seems like this empty property is not needed? (Won't it prevent someone doing msbuild /p:SourceBuildTargetFrameworks=customvalue if they want to experiment locally?)

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Won't it prevent someone doing msbuild /p:SourceBuildTargetFrameworks=customvalue

It won't prevent that because /p: wins all the time as it's a global property. Essentially it overrides whatever is in the project file and becomes a readonly property of build. It's very counterintuitive. The only way to get around this is to use TreatAsLocalProperty. Generally though that feature is not used very often, at least in our builds

@lewing
Copy link
Member

lewing commented Apr 13, 2023

this is still blocking the sdk change

@jaredpar jaredpar removed the untriaged Issues and PRs which have not yet been triaged by a lead label Apr 13, 2023
@jaredpar jaredpar merged commit a61229d into dotnet:main Apr 13, 2023
@ghost ghost added this to the Next milestone Apr 13, 2023
@jaredpar jaredpar deleted the sb branch April 13, 2023 14:12
rainersigwald added a commit to dotnet/msbuild that referenced this pull request Apr 21, 2023
As of dotnet/roslyn#67747, the name is just netcore.

Also simplified to use GeneratePathProperty.
rainersigwald added a commit to dotnet/msbuild that referenced this pull request Apr 21, 2023
@dibarbet dibarbet modified the milestones: Next, 17.7 P1 Apr 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants