Based on an offline conversation, it appears not having .cshtml / .razor files as Content items causes LSP-based Razor tooling to not function. We've seen a few incidents of users referencing the .NET SDK instead of Razor / Web SDK which results in no tooling. Moving the content includes in to the .NET SDK at the same place where the Compile Include default is configured would be one way to remedy the issue.