[BUG] Solution explorer not showing #808
Comments
|
Thanks @vriesj can you tell me what version of the extension you have as well? |
|
@timheuer I'm having trouble with the same problem. these are the version of vscode extensions. C# v2.14.8 |
|
Not sure if it's related, but in my case intellisense also does not work (maybe due to this issue)? |
|
@timheuer here is the output. Thanks. Activating C# + C# Dev Kit + C# IntelliCode... |
|
@imosan how about the output of |
|
@timheuer here is the result of "dotnet.ext --info" .NET SDK: ランタイム環境: インストール済みの .NET ワークロード: Host: .NET SDKs installed: .NET runtimes installed: Other architectures found: Environment variables: global.json file: Learn more: Download .NET: |
|
Thank you @imosan -- for your case, the dependencies look to be there. Can you share any more info about the workspace and projects within? If you create a new folder with a simple console app in it does it open without issue? Or a fairly full one with supported projects (https://github.com/timheuer/TestSolution) |
|
@timheuer When installing the Unity extension, it automatically installs the latest versions of C#, C# Dev Kit, IntelliCode for C# Dev Kit and Unity itself. |
|
@timheuer Extension version numbers dotnet --info |
|
Additionally I've tried to open your provided test solution (https://github.com/timheuer/TestSolution) in my environment which produces the same issue as in the original post and the following logs: Logs (click to expand)NuGet C# C# Dev Kit C# Dev Kit - Test Explorer C# LSP Trace Logs IntelliCode for C# Dev Kit Razor Log |
My logs look a bit different. If you feel mine is a different issue, let me know and I'll transfer it to a new ticket. Worth mentioning - mine is using the remote ssh extension to connect from MacOS -> Ubuntu. C# output C# DevKit dotnet info Attached is the crashreport. I can provide the dmp file too, but it's too large to attach here. |
Thanks! @jbevain can you take a look at this one? I think it might be project type support issue? |
@lukewis yes this looks different would you mind spawning a new issue with the great detail you put here. And wondering how we can find a way to get the dump...that looks like it might be helpful. If you could also add to that issue the project type, etc. and if a new/blank workspace with only a console app works for you (just trying to isolate simple -> complex) |
|
@timheuer I had a look a the test project provided by @imosan . This is not generated by us but rather by the default Unity project generator. And the project is a legacy style project so that's why this is not working with VSCode / C# Dev Kit. @imosan please have a look here to properly setup VSCode and Unity: The initial poster of this ticket @vriesj is not using Unity here if I'm not wrong, so I fear we are mixing up things in this ticket. |
I am indeed not using Unity. However if the behavior is the same, i.e. the solution explorer not loading, I think we should file it here under #808. If any projects in a solution are unable to load or incompatible it should still load as many projects as possible, similar to Honestly I'd rather see an entire stack track in the logs / pop-up instead of |
Moved my issue to #816. Sorry for the cross-pollination. |
@vriesj you are failing to even get some basic restores. I see PackageSourceMapping is enabled and indicating nuget.org not considered trying to resolve. Does restore even work from the command line on this solution? |
|
@timheuer I created a simple consoleApp1 in Visual Studio 2022 and opened it in vscode, but the result was exactly the same as in the case of a Unity project. Currently, it seems that the only way to address this issue here is through a method like the one described in the following link: |
|
@imosan you can certainly revert back to a version, but you'd no longer be using this extension (those instructions are to revert to an older language server extension), but we'd like you to use the unity setup per the note above. |
|
Any updates on this issue? ´´´ |
|
I also had this issue on my Mac for a couple of days and managed to solve it by: brew remove dotnetAnd then following the default installation steps in: https://learn.microsoft.com/en-us/dotnet/core/install/macos This is really weird as it seems Microsoft's C# Dev Kit is not able to use dotnet installations made by other tools, could it be relying on dotnet being on a specific location? |
|
Thank you @caiofbpa! This fixed it for me too. |
|
@caiofbpa THANK YOU! Your suggestion solved my similar problem. |
Describe the Issue
Probably related to #704 (closed)
When opening the solution explorer the following error appears.
And the solution explorer will fail to open:
C# log output
C# Dev Kit log output:
C# Dev Kit - Text Explorer log output
The
dotnet restorefailing might be related to dotnet/sdk#10189 which I've resolved manually via dotnet/sdk#10189 (comment) this however did not fix the solution explorer.Steps To Reproduce
No specific reproduction steps known other than a clean install.
Expected Behavior
No errors or UI bugs.
Environment Information
Windows 10 (22H2 19045.3693)
VS Code (in portable mode;
datadirectory)System also runs Visual Studio 2022
dotnet sdk's
The text was updated successfully, but these errors were encountered: