Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Use Roslyn v4.0 to build net6.0
See original GitHub issueSee https://github.com/dotnet/wpf/pull/5208#issuecomment-908626848. Targeting net6.0 is only supported using VS 2022, but the WPF repo is using VS 2019 in CI builds.
We should update the CI to use VS 2022 since targeting net6.0 requires using VS 2022.
Alternatively, we can update just the Roslyn version to ‘4.0’ while still using VS 2019.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Cross-Platform Code Generation with Roslyn and .NET Core
This article walks through the necessary steps to set up a C# project on .NET Core to use the Roslyn APIs and explains...
Read more >Incremental Roslyn Source Generators In .NET 6
The Roslyn Source Generators that came with the .NET 5 SDK help you to improve code sharing. Read about it in Pawel Gerr's...
Read more >Deploying Roslyn in application targeting .NET Framework ...
Now I would like to use Roslyn Compiler APIs to analyze and programatically build the assembly. I added the NuGet package Microsoft.CodeAnalysis ...
Read more >Using the Roslyn APIs to Analyse a .NET Solution
In this post, I demonstrate how to analyse a .NET solution using the .NET Roslyn APIs and a MsBuildWorkspace.
Read more >NET Build Improvement: Stop Wasting Resources
The .NET Build default behavior is wasting a lot of resources. Understand the problem and how to fix it. Be a minimalist developer....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ryalanms if this suggestion works, I highly recommend it since it’s a lot of work to keep VS 2022 images functional, and maybe not ideal to build official products with until it’s in GA. If you still find yourself needing an internal pool e.g.
buildpool.windows.amd64.vs2022.pre, let’s chat.Not only that, but we’ll also require a regular rebuild of wpf-int if we take the new dependency.