Closed Bram1903 closed 1 month ago
Hi @Bram1903, thank you for reporting! The problem is known and will be fixed in one of the upcoming 2024.3 EAP versions of Rider.
Hi @Bram1903, the support for .NET 9 projects Is merged and will become available in 2024.3 EAP5.
Great to hear. Thanks for letting me know!
Describe the bug
I am working on multiple projects, and today I updated one of them to .NET 9, following the release of .NET 9 Release Candidate 2. However, when trying to add a migration in the project targeting .NET 9, the target frameworks don't show up in the plugin. Initially, I suspected an installation issue, but after switching between projects using .NET 8 and .NET 9, it became evident that the issue only occurs with the .NET 9 plugin. I also tried removing both .NET 8 and .NET 9 to test the behavior, but the problem persisted. The same project works fine under .NET 8, but simply switching to the .NET 9 SDK renders the plugin unusable. Rider also displays a warning in the "Add migration" window when the project is set up to target .NET 9, as shown below:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
.NET 9 should appear as a valid target framework, and the startup project list should be populated.
Screenshots
.NET 8 (Working as expected):
.NET 9:
Environment: