Removing .Net install scripts

[Unslinga]

The plugin should not include scripts to install dotnet.

• Security Risk – Installing external software programmatically can introduce serious security vulnerabilities. Even if the scripts come from Microsoft.
• User Control – Users should manage their own development environment and dependencies.

It's better to document the required .NET version and prompt the user to install it manually if needed.

[gilzoide]

Hey @Unslinga thanks for the suggestion.

I agree we should let people install the .NET SDK manually if they want and allow them to provide an existing installation path, but to be honest I'd say we shouldn't force them to do so and provide the facility to just install the expected SDK with a simple button click.
We can change the behavior to avoid running the installation flow automatically and instead prompt users if they want to run the install script or provide the path of an existing installation.

Think of VSCode extensions for example, they just install the required .NET SDK to provide users with intellisense and everything else. Would you say they should also require people to install the SDK manually instead without giving the option to install it automatically? It's a much nicer UX providing the automatic installation.

On a diffent aspect of this discussion, would you feel safer if we implemented .NET SDK installation in C# editor code instead of running shell scripts?

[Unslinga]

In that case maybe I might be wrong in my assumption… I did some gargling and it seems to be “the correct way“ to install dotnet…

Maybe instead the option to install dotnet could be removed if the user already has dotnet installed…

[gilzoide]

I did some gargling and it seems to be “the correct way“ to install dotnet…

Oh, ok, interesting.

Maybe instead the option to install dotnet could be removed if the user already has dotnet installed…

Sure, that seems feasible =]