Code Actions Do Not Work for API/Site Projects

[terryaney]

Type: Bug

I have a workspace with a root .net8 api project (or site) which has project references to several other .net8 repositories (not found in path of api/site). I get code suggestions across all files/projects, but when I try to do an action in the api/site it doesn't give me option to perform the suggestion, while inside the same workspace, all suggestions are actionable in referenced 'library projects'.

VS Code version: Code 1.106.0 (ac4cbdf48759c7d8c3eb91ffe6bb04316e263c57, 2025-11-11T16:02:25.943Z)
OS version: Windows_NT x64 10.0.26100
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz (16 x 3600)
GPU Status	2d_canvas: enabled direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off trees_in_viz: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	63.94GB (14.90GB free)
Process Argv	--log info --crash-reporter-id 324c4641-8e15-4efb-9bdc-b30d565fb957
Screen Reader	no
VM	0%

Extensions (20)

Extension	Author (truncated)	Version
vs-code-intellisense-katapp	con	1.0.7
xml	Dot	2.5.1
gitlens	eam	17.7.1
dotnet-test-explorer	for	0.7.8
copilot	Git	1.388.0
copilot-chat	Git	0.33.1
rest-client	hum	0.25.1
rainbow-csv	mec	3.23.0
theme-monokai-pro-vscode	mon	2.0.10
csharp	ms-	2.100.5
vscode-dotnet-runtime	ms-	2.3.7
vscode-nuget-gallery	pat	1.2.4
vscode-xml	red	0.29.0
command-variable	rio	1.68.0
LiveServer	rit	5.7.9
vscode-coverage-gutters	rya	2.14.0
vscode-autohotkey2-lsp	thq	2.7.6
vscode-icons	vsc	12.15.0
volar	Vue	3.1.4
t4-support	zbe	0.7.0

A/B Experiments

vsliv368cf:30146710
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
aj953862:31281341
nes-set-on:31340697
onetestforazureexp:31335613
6abeh943:31336334
t123456:31413567
gaj49834:31404438
f1c06875:31397863
cloudbuttont:31379625
todos-1:31405332
v66_all_req:31402695
treatment_gpt5applypatchexclusively:31412086
42190218_ostrepl:31403339
trigger-command-fix:31379601
auto_model_enabled:31385282
use-responses-api:31390855
defaultusage:31403421
sonnet_45_3e700918:31419541
je187915:31401257
v2prompt_9f72f763:31415580
3i15c187:31419927
control_aa407747:31408711
673df989:31418077
nes-cd-200-0:31410879
copilot-nes-oct-t:31418199
ff8f5884:31411053
haab2303:31418916
expandedtokens:31420720
c0683394:31419495

My .workspace file looks like this:

{
	"folders": [
		{
			"path": "../../Api/WebService.Proxy",
			"name": "Api.WebService.Proxy"
		},
		{ "path": "../../Core" },
		{ "path": "../../Abstractions" },
		{ "path": "../../../GlobalConfiguration" },
		{ "path": "../../../Extensibility/JsonSchemas" }
	],
	"settings": {
		"dotnet-test-explorer.testProjectPath": "**/tests/*"
	},
	"launch": {
		"version": "0.2.0",
		"configurations": [],
		"compounds": []
	}
}

You can see below, when I click on problem from api/site, nothing is available:

But when I click on a referenced project, it is actionable:

Let me know if there is anything else I could provide to help diagnose.

[terryaney]

FYI - I upgraded project to .net 10 and same problem exists. Any information I can provide to help?

[dibarbet]

Apologies for the delay here, but I've been unable to reproduce this myself in API projects. A couple of things to check

1. If you open the file with the missing code actions, does the lightbulb menu show up in the editor at all with the correct actions?
2. Is it all code actions, or just some of them?
3. Could you verify that we're detecting files in the correct project (for the problematic one)? See https://github.com/dotnet/vscode-csharp/blob/main/SUPPORT.md#project-loading-problems

[terryaney]

I could be doing my 'apis' wrong. But for both my apis and my sites, I have:

<Project Sdk="Microsoft.NET.Sdk.Web">

Which I think brings in Razor Analyzers or something. I followed this comment to kind of work past my problem from omnisharp-roslyn repo, issue 2608. But just cumbersome for handful of reasons I could document if needed.

To answer your questions.

1. Code actions are there (light bulb, squigly blue underline) and rendered in editor, but ctrl+. just says 'no actions avail'. And images above show the problem with right click actions in 'problems' panel.
2. All code actions.
3. I'm not using DevKit. Let me know if you want me to research link more based on info given above.

[dibarbet]

3. I'm not using DevKit. Let me know if you want me to research link more based on info given above.

Yes, you should still be able to see the active project context without devkit, as in this screenshot

[dibarbet]

Which I think brings in Razor Analyzers or something. I followed this comment to kind of work past my problem from omnisharp-roslyn repo

Ah, are you using OmniSharp (as in dotnet.server.useOmnisharp is true)?

[terryaney]

Yes still using OmniSharp. I could dig into reasons again why I don't want DevKit (above and beyond licensing issues)...it just wasn't working the way I'd like it to.

And yes, basically my pattern now, is open workspace, immediately do OmniSharp: Select Project and 'build it' so that OmniSharp is happy. That along with the 'invalid razor path' setting, it is working. I discovered this workaround in between issue creation and your comment, so not sure if this is as good as I can get it or if you want some more info.

[JoeRobich]

For OmniSharp, I will say that multiple workspace folders isn't a well supported scenario. It very much expects the first folder to contain a solution file or all the projects that will be loaded. The version of OmniSharp shipping in the C# extension is a release behind. I recommend pulling down a local installation fro m https://github.com/OmniSharp/omnisharp-roslyn/releases/tag/v1.39.15 and configuring the dotnet.server.path setting appropriately.

Also note that Razor support in OmniSharp is not being actively improved at this point.

[terryaney]

a) I plan to evaluate DevKit again to see if it is working better (for my preferences) than it did during my original eval. Would you expect things to work better with DevKit if I still don't want to use *.sln files? Maybe I should bite the bullet and go back, but I've been liking/preferring simply a workspace file in place of a sln file...maybe it is just bad memories of sln management when I was in VS and .Net Framework solutions I work/ed on.

b) Additionally, if I have a different issue around code suggestions (the hover suggestion/problem item state the same suggestion, but when I try to apply the suggestion in the editor, it only offers OTHER suggestions. Is that an issue to report here? Or do I go to omnisharp? Or...?