-
Notifications
You must be signed in to change notification settings - Fork 676
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow rzls to launch using standard dotnet (Redo) #6844
Conversation
maryamariyan
commented
Feb 1, 2024
- Updates where to pick up dotnet.exe.
- Contributes to making rzls move away from being self-contained.
- Unifies how roslyn and razor servers acquire dotnet path/env variables.
- Picks up leftover changes from Allow rzls to launch using standard dotnet #5855 into main
- Updates where to pick up dotnet.exe. - Contributes to making rzls move away from being self-contained. - Unifies how roslyn and razor servers acquire dotnet path/env variables. - Picks up leftover changes from #5855 into main
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems reasonable to me!
vscode.l10n.t("Could not find Razor Language Server executable within directory '{0}'", withinDir) | ||
); | ||
} | ||
fullPath = path.join(withinDir, 'rzls.dll'); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a note here - it is possible to publish a non-self contained executable if you wanted to
https://learn.microsoft.com/en-us/dotnet/core/deploying/#publish-framework-dependent
The benefit of the executable is that your process name is the executable name. Whereas if you launch with dotnet rzls.dll
your executable name will be 'dotnet'