Don't register cohost types with the Razor project system #9830
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Part of #9519
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1939874
FYI @333fred
After talking to @DustinCampbell this morning I decided to slightly change tact with cohosting, and not worry about having it be able to co-exist with the current language server. That means this RPS regression is easy to fix just by disconnecting the cohost OpenDocumentGenerator from that system. Yes, that means co-hosting is now slightly worse, but if we move away from co-existence, then it matters a lot less, as we no longer expect it to fully work, it just needs to work enough to let us all get our work done. This PR doesn't change that.
In reality what this change does is that if cohosting is on, and the old server is off, then semantic tokens won't be correct for files that were already open when you stared VS. You have to close and reopen the file. No big deal IMO