December Iteration Plan

[webreidi]

Describe the Issue

Below is the list of items being worked on during December 2023 sprint. Not all items listed below will finish and release in December.

• [BUG] Dowload .NET Runtime always failed #138
• [BUG] Blazor Components are seen a unknown #49
• [BUG] Quick Fix Suggestion does not match to the specified framework/langVersion #419
• [SUGGESTION] Change debug default from integrated console for console apps or better message #585
• Run and Debug ignores environmentVariables in launchSettings.json #608
• [BUG] C# Devkit CommonAssemblyInfo.cs crash #650
• Restart debugging doesn't rebuild the project #496
• Latest Pre-Release cannot debug Blazor Web App #696
• C# Web API cannot connect to the server #718
• [BUG] Hot Reload is unable to find changes made to WeatherForecastController.cs #794
• I get asked which debugger to use on each new C# file #793
• [BUG] Run without debugging does not launches browser for Blazor & ASP.NET Web API #788
• [BUG] Improve readme content for readability #761
• Intellisense stopped working on deprecation of Omnisharp and update to C# Dev Kit #759
• [BUG] Tests with internal accessor are not discovered #725
• [BUG] Error message "Request textDocument/semanticTokens/range failed"  #722
• [SUGGESTION] Support Source Link with unit test debugging (or document how to set it up) #623
• Issue with using namespace where name is X.Y.Z.Windows #599
• Test explorer does not find tests in multi-folder solution #538
• Solution explorer doesn't show source generated files #362
• [BUG] C# dev kit for xUnit not discovering tests #307
• C# DevKit suggests refactorings that break build/don't compile #305
• [BUG] Tests error not showing with Moq #278

See also, C# extension December 2023 Iteration Plan

Steps To Reproduce

No response

Expected Behavior

No response

Environment Information

No response