You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are instances where csharpier is partially installed and if fails to run. This is the output from VSCode
["WARN" - 5:05:10 PM] Exception while running 'dotnet csharpier --version' in C:\Users\<WITHHELD>\AppData\Local\CSharpier\0.20.0
"Cannot use file stream for [C:\\Users\\<WITHHELD>\\AppData\\Local\\CSharpier\\0.20.0\\.store\\csharpier\\0.20.0\\csharpier\\0.20.0\\tools\\net6.0\\any\\dotnet-csharpier.deps.json]: No such file or directory\r\nA fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\\Program Files\\dotnet\\'.\r\nFailed to run as a self-contained app.\r\n - The application was run as a self-contained app because 'C:\\Users\\<WITHHELD>\\AppData\\Local\\CSharpier\\0.20.0\\.store\\csharpier\\0.20.0\\csharpier\\0.20.0\\tools\\net6.0\\any\\dotnet-csharpier.runtimeconfig.json' was not found.\r\n - If this should be a framework-dependent app, add the 'C:\\Users\\<WITHHELD>\\AppData\\Local\\CSharpier\\0.20.0\\.store\\csharpier\\0.20.0\\csharpier\\0.20.0\\tools\\net6.0\\any\\dotnet-csharpier.runtimeconfig.json' file and specify the appropriate framework.\r\n"
["ERROR" - 5:05:10 PM] ,,Tool 'csharpier' is already installed.
["DEBUG" - 5:05:10 PM] returning NullCSharpierProcess because of the previous error when trying to set up a csharpier process
The extensions install csharpier to a custom directory because they keep the dotnet tool running in the background. If they kept csharpier running from the default location then a user will run into issues if they run commands to update csharpier.
Testing the install can be done with the following command
There are instances where csharpier is partially installed and if fails to run. This is the output from VSCode
The extensions install csharpier to a custom directory because they keep the dotnet tool running in the background. If they kept csharpier running from the default location then a user will run into issues if they run commands to update csharpier.
Testing the install can be done with the following command
Deleting that directory and restarting VSCode would get the extension to reinstall csharpier in the custom location.
It should be possible for the extensions to detect this and attempt to delete and reinstall csharpier.
The text was updated successfully, but these errors were encountered: