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.

Sign up for GitHub

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

Jump to bottom

Changing project order in solution makes the build fail #36

Open
chtenb opened this issue Feb 24, 2021 · 7 comments
Open

Changing project order in solution makes the build fail #36

chtenb opened this issue Feb 24, 2021 · 7 comments
Labels
upstream

Comments

@chtenb
Copy link
Member

chtenb commented Feb 24, 2021 •
edited
Loading

#33 reproduces the issue.

This problems only occurs when executing MSBuild Rubjerg.Graphviz.sln from the commandline (Developer Command Prompt for VS 2019).
From within Visual Studio the build always succeeds.
MSBuild version is the newest: 16.8.3.61104
@chtenb
Copy link
Member Author

chtenb commented Feb 24, 2021

Project build order on master according to VS:
image
On PR:
image

@chtenb
Copy link
Member Author

chtenb commented Feb 25, 2021

Top lines of diff of build logs
image

@chtenb
Copy link
Member Author

chtenb commented Feb 25, 2021

Issue filed: https://github.com/dotnet/project-system/issues/6988

@chtenb
Copy link
Member Author

chtenb commented Mar 2, 2021

Issue has been moved: dotnet/msbuild#6198

@chtenb
Copy link
Member Author

chtenb commented Jul 10, 2021 •
edited
Loading

Related issue: dotnet/msbuild#1054
With fix: dotnet/msbuild#6622

@chtenb chtenb mentioned this issue Aug 6, 2022
Open
@chtenb chtenb added the upstream label Aug 2, 2023
@KirillOsenkov
Copy link

See if dotnet/msbuild#9709 is related

@SimaTian
Copy link

SimaTian commented Jan 9, 2025

Hello, I've created a fix PR for the issue with some comments.
Probably not necessary to merge, however since it isn't fix related to changing MSBuild code but rather to working with the .csproj files, this was the only place to put it to give it visibility.

My analysis of the solution and why I think it works is within the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
upstream
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@KirillOsenkov @chtenb @SimaTian