[O# Parity] Support loading non-solution based projects/files

[dibarbet]

Currently the C# extension's project loading capabilities only supports loading full solution files. O# supports loading csproj files.

CSX support is tracked here - #6411

[alexrp]

I see this is in "feature backlog", so I just want to ask what that means in terms of prioritization?

I use Traversal for basically every project I work on these days, which works great under OmniSharp since it can load loose project files, and in VS with Open Folder too. It would be unfortunate to have to take a step backwards and maintain solution files in order to use the new Roslyn-based LSP host. (FWIW, judging by the reactions on microsoft/vscode-dotnettools#121, others are in the same boat.)

[v-Judy]

@dibarbet After installed the C# Dev Kit(v 0.5.2) with C# extension (v 2.1.2), when I want to run and debug the project, an error Cannot create .NET debug configurations. The active C# project is not within folder occurred.
Based on the 6050 comment, I try to add a solution and add the project to the solution, also set the dotnet.server.useOmnisharp option to get back the old behavior which can load projects, but it does not works for me.

If I only install the C# extension(v 2.1.2), this issue does not repro.

This issue only repro on Mac OS and does not repro on Linux and Windows OS. I'm not sure whether it's a same issue. Should I create a new issue to track it?

[jasonmalinowski]

@v-Judy Please file a new bug for this.

[v-Judy]

@v-Judy Please file a new bug for this.

Thanks for your reply! I will file a new bug 6314 for it.

[vpetit-reimagine]

I have the same issue, without ever installing the C# Dev Kit extension but only the C# v2.1.2. I have a .sln at the root of the currently opened folder, and 2 projects in their own subfolders, referenced by the .sln.

This is utterly annoying that this is broken.

[jasonmalinowski]

I have the same issue, without ever installing the C# Dev Kit extension but only the C# v2.1.2. I have a .sln at the root of the currently opened folder, and 2 projects in their own subfolders, referenced by the .sln.

This is utterly annoying that this is broken.

@vpetit-reimagine Can you file a new bug for us to track and with the details in our template? Sounds like this is different than the feature gap we're trying to track here.

[vpetit-reimagine]

I have the same issue, without ever installing the C# Dev Kit extension but only the C# v2.1.2. I have a .sln at the root of the currently opened folder, and 2 projects in their own subfolders, referenced by the .sln.
This is utterly annoying that this is broken.

@vpetit-reimagine Can you file a new bug for us to track and with the details in our template? Sounds like this is different than the feature gap we're trying to track here.

Here it is #6403.

[aelij]

I would love it if the C# extension would be able to open any MSBuild project file that contains project references (with or without the Traversal SDK - by utilizing the MSBuild static graph feature) and create a "dynamic solution" that is updated live when the project references change on disk (for example, a new .csproj file is created).

Solution files are cumbersome and hard to use, and we never create them manually. We currently have to rely on slngen which creates static solution files. When we pull from source control, we get restore errors due to missing projects in the .sln file on disk.

I've opened a similar issue for VS which has gotten many votes.

[jasonmalinowski]

@aelij Yep, we're tracking that work with #6008.