Using statements not showing up for ctrl-.
See original GitHub issueI’m still seeing issues with using statements not showing up in the lightbulb menu for new .NET Core projects
Steps to reproduce:
- Install .NET Core 2.0 SDK
dotnet new console
dotnet add package Microsoft.AspNetCore.All
- In
Program.Main
typeWebHost
and try to resolve the using statement forWebHost
.
Expected result
- Lightbulb to add
using Microsoft.AspNetCore
Actual result
- No helpful lightbulb to add the using statement
- Waiting doesn’t help
Workaround:
- Closing and reopening the folder causes the using statements to start to show up
Issue Analytics
- State:
- Created 6 years ago
- Comments:8 (8 by maintainers)
Top Results From Across the Web
Where are the using statements/directives in .NET 6
I am aware that I am not showing you all my code, but I was able to build and run something that looks...
Read more >Add reference using Ctrl + . not working
2, trying to add a reference using the shortcut Ctrl + . will not work. It shows the dialog add references to Assembly...
Read more >Implicit Using Statements In .NET 6 -.NET Core Tutorials
One of the newest features in .NET 6 is an implicit global using statement. This article takes a look at what this means...
Read more >using statement - C# Reference | Microsoft Learn
Within the using block, the object is read-only and can't be modified or reassigned. A variable declared with a using declaration is read-only....
Read more >Quick Tip - Remove Unused Using References in Visual Studio
When working on a C# project be it Xamarin, ASP.NET Core etc within Visual Studio, developers sometimes forget to clean up using statements....
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 FreeTop 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
Top GitHub Comments
This issue has been fixed in the 1.14 milestone. We just released our first beta of 1.14 if you’re interested in giving it a spin. Follow these instructions to a beta release of C# for VS Code.
Still got this issue in beta2. vscode 1.19.1