After merging task scanning to be in-process work we now don't spawn any additional processes for us (except checking installed .NET version on user's machine, but it is obviously intended to use any .NET version). Since starting LSP is done using isolated runtime from .NET Runtime extension, we do not require end user to have any specific version of .NET to be installed anymore
We may need to keep an eye out for any odd behaviour caused by forward-compatibility issues with new runtime issues, but that shouldn't be too difficult.
After merging task scanning to be in-process work we now don't spawn any additional processes for us (except checking installed .NET version on user's machine, but it is obviously intended to use any .NET version). Since starting LSP is done using isolated runtime from .NET Runtime extension, we do not require end user to have any specific version of .NET to be installed anymore