Skip to content

[Dev-Docs AI Improvement]: Debug background processes using Microsoft Visual Studio #13898

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
docsautomation wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Dev-Docs AI Improvement]: Debug background processes using Microsoft Visual Studio #13898

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions msteams-platform/toolkit/toolkit-v4/debug-background-process-vs.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,9 @@ ms.date: 03/03/2022

# Debug background processes using Microsoft Visual Studio

Visual Studio uses the `launchSettings.json` file to store configuration information that describes how to start an ASP.NET Core application. The file holds essential application settings used solely during development on the local machine. You can find it in the Properties folder of your project. It specifies details like the command to run, the browser's URL, and the required environment variables to be set.
Visual Studio uses the `launchSettings.json` file to store configuration information that describes how to start an ASP.NET Core application. This file holds essential application settings used solely during development on the local machine. You can find it in the Properties folder of your project. It specifies details like the command to run, the browser's URL, and the required environment variables to be set.

After selecting **Select Microsoft 365 Account**, Microsoft 365 Agents Toolkit updates the launchUrl using the real Microsoft Teams app ID, Teams tenant ID, and Microsoft 365 account.
After selecting **Select Microsoft 365 Account**, Microsoft 365 Agents Toolkit updates the `launchUrl` using the real Microsoft Teams app ID, Teams tenant ID, and Microsoft 365 account.

## Start local tunnel

Expand All @@ -29,7 +29,7 @@ The tunnel creation dialog opens.
* Select the **Account** to use to create the tunnel. Azure, Microsoft Account (MSA), and GitHub are the account types that are supported.
* Enter a **Name** for the tunnel.
* Select the **Tunnel Type**, Persistent or Temporary.
* From the dropdown, select the required public authentication in **Access**.
* From the dropdown, select the required public authentication in **Access**.
* Select **OK**. Visual Studio displays confirmation of tunnel creation.

The tunnel you create is under **Dev Tunnels(MyPublicDevTunnel)** > **MyPublicDevTunnel**.
Expand All @@ -56,4 +56,4 @@ You can view the project folders and files under **Explorer** in Visual Studio a
* [Debug your Teams app locally using Visual Studio](debug-local-vs.md)
* [Provision cloud resources in Visual Studio](provision-vs.md)
* [Deploy Teams app to the cloud VS](deploy-vs.md)
* [Customize app manifest in Teams Toolkit](TeamsFx-preview-and-customize-app-manifest-vs.md)
* [Customize app manifest in Teams Toolkit](TeamsFx-preview-and-customize-app-manifest-vs.md)