Skip to content
This repository has been archived by the owner on May 21, 2024. It is now read-only.

Sniff for dotnet-sdk and don't do what OmniSharp already does #20

Merged
merged 1 commit into from
Jun 14, 2021

Conversation

cartermp
Copy link
Contributor

Something in the latest VSCode creates problems when we try to call this command unconditionally.

Also, we should not be restarting the O# server according to @JoeRobich

@@ -58,12 +63,6 @@ async function initializeDependencies() {

// Acquire .NET Interactive
initializeDependency("ms-dotnettools.dotnet-interactive-vscode", "dotnet-interactive.acquire", sdkResult?.dotnetPath);

// Start OmniSharp
initializeDependency("ms-dotnettools.csharp", "o.restart");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be useful to activate the C# extension to kick off dependency acquisition. However, there is no need to execute either of the commands.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I'm thinking we should just not do that for now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, confirmed that this works without issue. I will merge this and publish an update, since functionally this doesn't really change things other than no longer causing this conflict.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants