-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Activating the "Microsoft.VisualStudio.ProjectSystem.Query.Remoting.QueryExecutionService (0.2)" service failed. #840
Comments
to clarify, the issue happens with or without specifying DOTNET_ROOT it happens on multiple repos as well. Let me know what logs I can share to help figure this out, this is really impacting my productivity |
This issue has been marked as stale after 14 days of inactivity. @[ @ @], could you please take a look? |
@lifengl Can you check to see if we've fixed this issue (or if it still repros? |
I am also having this issue now on a Unity project. Was fine yesterday. If I uninstall the Unity extension, and then uninstall the c# dev kit extension, then reinstall them both and reload extensions everything works until the next time I close and re-open VSCode. |
Installed v1.4.29 and everything worked fine! |
Thanks for the heads up. That seems to be working fine for me now. |
Can confirm with my Unity project that using v1.5.20 of the C# Dev Kit extension no longer works, but manually downgrading v1.4.29 fixed things. |
FWIW downgrading C# Dev Kit to v1.4.29 fixed my similar issues. Using "straight" c#, no Unity or web or anything. |
Based on the information posted earlier, it looks like the project system failed to load. Based on the timeline, it is about the time when the project system hosting process was updated to support Aspire projects, but there are also many other things happening about the same time. To understand what was going on, we need help if anyone running into this issue could send us some log files from the extension. In the session when the extension failed, use vscode command "open extension logs folder", and browse into ms-dotnettools.csdevkit\ServiceHub sub-folder, the first interesting one is named like this: -hubController--*-1.log this file should capture some command line information to start the project system process. The second one is named like -dotnet--*-1.log, which contains the initial logging of the project system hosting process. The third one is named like -Microsoft.VisualStudio.ProjectSystem.CompositionService--*-1.log, including the project system initialization log. If the system failed earlier, the later log files might be missing. Or, the earlier log might show things working, and a later failure point might be logged in a later log file. if anyone can help to provide some content of those files, (or sometime, an exception with call stack in one of that would help us to narrow down what is going on. also output of dotnet --info might help. Although the original issue was reported from a non-windows platform, the later screen-shot is clearly from a windows machine. The dotnet info command provide some version information of dotnet SDK installed on the machine, sometime, we may not aware of problems when the extension might be broken on a slightly older runtime... |
@mertdorukkalkan Go to the "C# dev Kit" extension in VSCode. Next to the Uninstall button is a pulldown that will let you install a different version. |
Maybe the extension requires The naming convention is too difficult for me to understand. |
@Doekin , that is what I thought. The difference between 1.5.20 and 1.4.29 is that the newer version requires ASP.NET runtime. Usually, APS.NET would be installed when .NET SDK is installed. Can you run dotnet --info, which may explain what has been installed on the machine? |
hmm... I guess one possibility is that the machine has NET 8 Core runtime, but no ASP.NET runtime. Because ASP.NET runtime is installed with SDK, so maybe the machine running into this problem has newer runtime + older SDKs? I wonder maybe certain configuration confused the extension so it picks up a wrong runtime configuration. |
Same problem on Arch, fixed by installing |
@lifengl I finally had a chance to gather logs as you suggested. Starting the 1.5.20 version I get:
After installing .NET SDK 8.0 everything works fine now. |
While the team is working on a fix, to work around this issue: |
Thank you! works fine with v1.4.29 |
Yes, everything worked for me after installation, too.NET SDK |
I was getting the Thanks! |
Note that the latest prerelease version (currently 1.7.4) has a fix such that the ASP.NET runtime will only be needed if you are launching/debugging Aspire app host projects. This bug will be closed when that fix makes it to a release version. |
Describe the Issue
This is copied from a comment on dotnet/vscode-csharp#6777 (comment), originally posted by @dpoole73
I do see this error when opening code:
Activating the "Microsoft.VisualStudio.CpsProjectIconSourceService (0.1)" service failed.
I also see this in the C# Dev Kit - Test explorer log:
Likely because there is no solution shown in the solution explorer is why the Language server is not working?
Steps To Reproduce
No response
Expected Behavior
No response
Environment Information
i'm seeing very similar issues. I'm running on MacBook with apple silicon using the x64 version of dotnet and setting DOTNET_ROOT
The text was updated successfully, but these errors were encountered: