Solution launch profile has incorrect name

[TPIvan]

Describe the bug
When a project is created in Visual Studio the created .slnLaunch.user has name of created project not the name of created .sln. The consequence is that the launch configurations (e.g. "Microsoft Teams (browser)") are not available.
Example:
I am creating project called EchoBot in solution EchoBotSolution so my .sln is EchoBotSolution.sln and EchoBotSolution.slnLaunch.user should be created but EchoBot.slnLaunch.user is created instead.

To Reproduce
Steps to reproduce the behavior:

1. Open New instance of Visual Studio
2. Click on 'Create a new project'
3. Select 'Microsoft 365 Agents'
4. On 'Configure your new project' screen uncheck 'Place solution and project in the same directory', set 'Project name' EchoBot, 'Solution name' EchoBotSolution
5. Press Create
6. Select App type 'Echo Bot' and press Create
7. In the Visual Studio which opens check Configuration dropdown. "Microsoft Teams (browser)" and other configurations are missing
8. Check the solution folder here you see files EchoBotSolution.sln and EchoBot.slnLaunch.user

Expected behavior
Configuration contains "Microsoft Teams (browser)" . So the files in solution folder should be EchoBotSolution.sln and EchoBotSolution.slnLaunch.user

Screenshots

Visual Studio Extension Information (please complete the following information):

• OS: [Windows]
• Version [Version 10.0.19045 Build 19045]
• Visual Studio Version 17.14.3

CLI Information (please complete the following information):

• OS: [Windows]
• Version [Version 10.0.19045 Build 19045]

[m365-agent-toolkit-assistant]

👋 Hi @TPIvan,

Thank you for reporting this issue! We want to let you know that:

⏱️ Our team will personally review your issue
🎯 You can expect a response within 2 business days

✨ This is an AI-generated initial response
🤖 AI-Generated Preliminary Analysis:

Known Issue: Solution Launch Profile Has Incorrect Name

Issue Summary:

The issue reported is that when creating a new Microsoft 365 Agent project in Visual Studio, the .slnLaunch.user file is named after the project instead of the solution, causing launch configurations (e.g., "Microsoft Teams (browser)") to be unavailable.

Steps to Reproduce:

1. Open a new instance of Visual Studio.
2. Create a new project, selecting 'Microsoft 365 Agents'.
3. In 'Configure your new project', uncheck 'Place solution and project in the same directory', set Project name to EchoBot and Solution name to EchoBotSolution.
4. Create the project and select 'Echo Bot' as the app type.
5. Check the Configuration dropdown; the necessary configurations are missing.
6. Observe the solution folder where files EchoBotSolution.sln and EchoBot.slnLaunch.user exist.

Expected Behavior:
The configuration should contain "Microsoft Teams (browser)", and the solution folder should have files EchoBotSolution.sln and EchoBotSolution.slnLaunch.user.

Proposed Workaround:
Rename the .slnLaunch.user file from EchoBot.slnLaunch.user to EchoBotSolution.slnLaunch.user manually. This could help ensure the configurations are linked correctly.

Actionable Steps:

1. Navigate to the solution folder.
2. Rename EchoBot.slnLaunch.user to EchoBotSolution.slnLaunch.user.
3. Open Visual Studio and reload your project to see if the configurations are now available.

If renaming the file does not resolve the issue, you may need to manually recreate the launch configurations in the newly named .slnLaunch.user file.

Example Renaming Steps:

1. Close Visual Studio.
2. Open File Explorer and navigate to your solution directory.
3. Right-click EchoBot.slnLaunch.user and select 'Rename'.
4. Change the name to EchoBotSolution.slnLaunch.user.
5. Open Visual Studio and load your solution again.

If the issue persists despite the workaround, consider logging it as a bug or feature request to the Teams Toolkit for Visual Studio GitHub repository.

For continued issues, please verify you are using the latest version of the Teams Toolkit and Visual Studio, and consider providing error logs for more detailed troubleshooting.

✨We'd love your feedback! Please take a moment to fill out our survey.

---

Note: This is an automated first response generated by AI. A human team member will review your issue and provide a more detailed response soon. We appreciate your patience!

[Nivedipa-MSFT]

@TPIvan - Thanks for bringing this issue to our attention. We will check and update you soon.

[HuihuiWu-Microsoft]

Hi @TPIvan Thanks for reporting this to us. This is a bug from our side and will be fixed in next release.