Closed Youssef1313 closed 3 years ago
Running a build task also fails for me:
> Executing task: powershell D:\dotnet\Roslyn/scripts/vscode-build.ps1 -filePath d:\dotnet\Roslyn\src\EditorFeatures\CSharpTest\Completion\CompletionProviders\DeclarationNameCompletionProviderTests.cs -msbuildEngine dotnet <
D:\dotnet\Roslyn/scripts/vscode-build.ps1 : File D:\dotnet\Roslyn\scripts\vscode-build.ps1 cannot be loaded. The file
D:\dotnet\Roslyn\scripts\vscode-build.ps1 is not digitally signed. You cannot run this script on the current system. For more information
about running scripts and setting execution policy, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170.
At line:1 char:1
+ D:\dotnet\Roslyn/scripts/vscode-build.ps1 -filePath d:\dotnet\Roslyn\ ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command powershell D:\dotnet\Roslyn/scripts/vscode-build.ps1 -filePath d:\dotnet\Roslyn\src\EditorFeatures\CSharpTest\Completion\CompletionProviders\DeclarationNameCompletionProviderTests.cs -msbuildEngine dotnet" terminated with exit code: 1.
The instructions here doesn't seem to state that there is something special I have to do to get it working.
I won't expect OmniSharp to perform correct or effectively for complicated customized project. It once consumed 30GB of memory when opening runtime repo.
Instructions here would imply that VS Code will work correctly for Roslyn repo. I also remember that someone in Roslyn's team is using VS Code (either @333fred or @RikkiGibson - or might be both - can't remember correctly).
It once consumed 30GB of memory when opening runtime repo.
I don't even have this much of RAM :smile:
I haven't needed to do anything particularly special to get O# to work with roslyn. Have you done a .\restore
and .\build
yet? As to signing, that's a powershell config concept: https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set-executionpolicy?view=powershell-7.1. You'll want set an execution scope of at least RemoteSigned
(all downloaded files must be signed, local files do not need to be signed).
@Youssef1313 Sorry you are running into issues. Typically, when we see [ERROR] Error: command 'omnisharp.runCodeAction' already exists
that means there are multiple VS Code windows open where one may have upgraded to a different version of the extension. I would recommend closing all VS Code completely and reopening.
Have you done a
.\restore
and.\build
yet
Yes I had done that.
You'll want set an execution scope of at least RemoteSigned (all downloaded files must be signed, local files do not need to be signed).
@333fred Thanks! That helps a lot.
@JoeRobich Thanks a lot. When I opened it that time it did a version update, I tried again and :hooray: the error is gone, and IntelliSense is working now.
Thanks again both @333fred and @JoeRobich
OmniSharp log:
Trying to run a test gives the following error:
Trying to debug a test only shows
Debugging test(s) in context .....
message without any further errors.Restarting OmniSharp server doesn't help.
Note: IntelliSense is also not working for me.