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

Set BuildingInsideVisualStudio to load WPF projects #1390

Closed
wants to merge 4 commits into from

Conversation

JoeRobich
Copy link
Member

Resolves #1337

@JoeRobich JoeRobich changed the base branch from main to release/6.x October 18, 2021 22:26
@JoeRobich JoeRobich force-pushed the load-wpf-projects branch 6 times, most recently from 2c4cb2b to d5fc5af Compare October 23, 2021 00:31
@JoeRobich JoeRobich force-pushed the load-wpf-projects branch 2 times, most recently from 6508d53 to 853097f Compare October 23, 2021 02:33
@JoeRobich
Copy link
Member Author

Split workspace loader tests out and rebased on #1401

@JoeRobich
Copy link
Member Author

Taking this PR would cause the same regressions in blazor and blazorwasm scenarios as described in dotnet/roslyn#69225 (comment). I would prefer to see dotnet/roslyn#69225 merge in as it does not regress project loading.

@JoeRobich
Copy link
Member Author

Closing in favor of a fix in Roslyn itself (dotnet/roslyn#69225)

@JoeRobich JoeRobich closed this Oct 23, 2023
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 this pull request may close these issues.

WPF projects don't compile
1 participant