The startup experience at launch in C# and C#DevKit, as well as other extensions that rely on the .NET Install Tool, received a large level of focus this quarter. For the median user we have saved at least 800+ ms from startup time with the existing work, but much more for the percentile of users with slower computers or networks.
This also involves the update and download experience, which can be improved from the current state of needing to check for a new .NET runtime every time that C# and C#DK are initialized. This check and update can take minutes for many users leading to a bad experience.
Investments were also made to 'async' up the codebase and properly implement a safe mutex experience across multiple windows of vscode/code insiders simultaneously while handling process kill scenarios better, which all also tied to the performance story.
Issues:
Unresolved:
The startup experience at launch in C# and C#DevKit, as well as other extensions that rely on the .NET Install Tool, received a large level of focus this quarter. For the median user we have saved at least 800+ ms from startup time with the existing work, but much more for the percentile of users with slower computers or networks.
This also involves the update and download experience, which can be improved from the current state of needing to check for a new .NET runtime every time that C# and C#DK are initialized. This check and update can take minutes for many users leading to a bad experience.
Investments were also made to 'async' up the codebase and properly implement a safe mutex experience across multiple windows of vscode/code insiders simultaneously while handling process kill scenarios better, which all also tied to the performance story.
Issues:
dotnet --infoby using--list-x --archwhen available vscode-dotnet-runtime#2296Unresolved:
dotnetSDKPathSetting for User SDKs and Projects vscode-dotnet-runtime#2354