Allow selection of .csproj for dotnet commands

[Crashdummyy]

trafficstars

Most projects often contain more than one csproj file and remain somewhere at the solution level with their cwd. This makes options 5-7 fail a lot ( at least in my case ).

This extends the current behavior by providing a filepicker.

[Crashdummyy]

It's more expensive but we could reduce the selections for the dotnet run command ( or all of them ? ) somewhat further by only providing those csproj. that are actually executable.

We have to maintain a list of the sdks tho which is why I didnt implement it this way.

We either have to look for an existing OutputType node

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
  </PropertyGroup>

</Project>

Or a sdk target that actually supports executing, eg <Project Sdk="Microsoft.NET.Sdk.Web">

[Crashdummyy]

Closing this due to lack of interest

[Zeioth]

@Crashdummyy Sorry for taking so long. I got a day job and development is gonna slow down a for the next months. I will have some days to look into it during christmas. Thank you for sending it.

[Crashdummyy]

@Crashdummyy Sorry for taking so long. I got a day job and development is gonna slow down a for the next months. I will have some days to look into it during christmas. Thank you for sending it.

Thanks a lot for that but you really dont need to do this if you dont have time for it. It was just a tiny convenience function :)