Skip to content

Store "Configure Multiple Startup Projects" settings on the SLN file itself #61250

Open
@mattvarghese

Description

@mattvarghese

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

A new React and ASP.NET Core (TypeScript) solution in VS2022contains separate frontend (esproj) and backend (csproj) projects. To run this and debug it, one must do Solution > Configure Startup Projects > Multiple Startup Projects - and select both to Start. This is configured by default when creating a new solution with this project template. So all of this works fine.

However, we hit a problem when checking this code into source control. The multiple startup projects configuration is NOT stored on the .sln file. Rather it is stored in the .vs/{projectname}/v17/.suo file. Most organizations commit neither the .vs folder nor any *.suo files to source control. This means

  1. it is a step that the developer must do every time they checkout code, and
  2. it also requires that the dev know how to do this, which as I found not everyone knows.

Expected Behavior

Could we please move this setting to the .sln file itself?
That way it is also tracked in source control.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

This is my first issue on ASP.NET Core. So apologies if I'm making it / providing some detail incorrectly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-area-labelUsed by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions