You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/debugger/debug-live-azure-apps-faq.md
+140-2Lines changed: 140 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -43,18 +43,156 @@ Yes, snapshot debugging can work for servers under load. The Snapshot Debugger t
43
43
44
44
You can uninstall the Snapshot Debugger site extension on your App Service with the following steps:
45
45
46
-
1. Turn off your App Service either through the Cloud Explorer in Visual Studio or Azure portal.
46
+
1. Turn off your App Service either through the Cloud Explorer in Visual Studio or the Azure portal.
47
47
1. Navigate to your App Service's Kudu site (that is, yourappservice.**scm**.azurewebsites.net) and navigate to **Site extensions**.
48
48
1. Click the X on the Snapshot Debugger site extension to remove it.
49
49
50
50
#### Why are ports opened during a Snapshot Debugger session?
51
51
52
52
Snapshot Debugger needs to open a set of ports in order to debug the snapshots taken in Azure, these are the same ports required for remote debugging. [You can find the list of ports here](../debugger/remote-debugger-port-assignments.md).
53
53
54
+
#### How do I disable the Remote Debugger extension?
55
+
56
+
For App Services:
57
+
1. Disable Remote Debugger extension via the Azure portal for your App Service.
58
+
2. Azure portal > your Application Service resource blade > *Application Settings*
59
+
3. Navigate to the *Debugging* section and click the *Off* button for *Remote debugging*.
60
+
61
+
For AKS:
62
+
1. Update your Dockerfile to remove the sections corresponding to the [Visual Studio Snapshot Debugger on Docker images](https://github.com/Microsoft/vssnapshotdebugger-docker).
63
+
2. Rebuild and redeploy the modified Docker image.
64
+
65
+
For virtual machine/virtual machine scale sets remove the Remote Debugger extension, Certificates, KeyVaults and InBound NAT pools as follows:
66
+
67
+
1. Remove Remote Debugger extension
68
+
69
+
There are several ways to disable the Remote Debugger for virtual machines and virtual machine scale sets:
70
+
71
+
- Disable the Remote Debugger through Cloud Explorer
72
+
73
+
- Cloud Explorer > your virtual machine resource > Disable Debugging (Disabling Debugging does not exist for virtual machine scale set on Cloud Explorer).
74
+
75
+
76
+
- Disable the Remote Debugger with PowerShell Scripts/Cmdlets
> Virtual machine scale sets - The portal does not allow removing the DebuggerListener ports. You will need to use Azure PowerShell. See below for details.
98
+
99
+
2. Remove Certificates and Azure KeyVault
100
+
101
+
When installing the Remote Debugger extension for virtual machine or virtual machine scale sets, both client and server certificates are created to authenticate the VS client with the Azure Virtual Machine/virtual machine scale sets resources.
102
+
103
+
- The Client Cert
104
+
105
+
This cert is a self-signed certificate located in Cert:/CurrentUser/My/
- The corresponding server certificate thumbprint is deployed as a secret to Azure KeyVault. VS will attempt to find or create a KeyVault with prefix MSVSAZ* in the region corresponding to the virtual machine or virtual machine scale sets resource. All virtual machine or virtual machine scale sets resources deployed to that region therefore will share the same KeyVault.
123
+
- To delete the server certificate thumbprint secret, go to the Azure portal and find the MSVSAZ* KeyVault in the same region that's hosting your resource. Delete the secret which should be labeled `remotedebugcert<<ResourceName>>`
124
+
- You will also need to delete the server secret from your resource via PowerShell.
1. Disable Snapshot Debugger via the Azure portal for your App Service.
160
+
2. Azure portal > your Application Service resource blade > *Application Settings*
161
+
3. Delete the following App settings in the Azure portal and save your changes.
162
+
- INSTRUMENTATIONENGINE_EXTENSION_VERSION
163
+
- SNAPSHOTDEBUGGER_EXTENSION_VERSION
164
+
165
+
> [!WARNING]
166
+
> Any changes to Application Settings will initiate an app restart. Details about Application Settings can be found [here](https://docs.microsoft.com/azure/app-service/web-sites-configure#app-settings).
167
+
168
+
For AKS:
169
+
1. Update your Dockerfile to remove the sections corresponding to the [Visual Studio Snapshot Debugger on Docker images](https://github.com/Microsoft/vssnapshotdebugger-docker).
170
+
2. Rebuild and redeploy the modified Docker image.
171
+
172
+
For virtual machine/virtual machine scale sets:
173
+
174
+
There are several ways to disable the Snapshot Debugger:
175
+
- Cloud Explorer > your virtual machine/virtual machine scale set resource > Disable Diagnostics
176
+
177
+
- Azure portal > your virtual machine/virtual machine scale set resource blade > Extensions > Uninstall Microsoft.Insights.VMDiagnosticsSettings extension
178
+
179
+
- PowerShell Cmdlets from [Az PowerShell](https://docs.microsoft.com/powershell/azure/overview)
- [Debugging in Visual Studio](../debugger/index.md)
57
195
- [Debug live ASP.NET apps using the Snapshot Debugger](../debugger/debug-live-azure-applications.md)
58
-
-[Debug live ASP.NET Azure Virtual Machines\Virtual Machines Scale Sets using the Snapshot Debugger](../debugger/debug-live-azure-virtual-machines.md)
196
+
- [Debug live ASP.NET Azure Virtual Machines\Virtual Machines scale sets using the Snapshot Debugger](../debugger/debug-live-azure-virtual-machines.md)
59
197
- [Debug live ASP.NET Azure Kubernetes using the Snapshot Debugger](../debugger/debug-live-azure-kubernetes.md)
60
198
- [Troubleshooting and known issues for snapshot debugging](../debugger/debug-live-azure-apps-troubleshooting.md)
Copy file name to clipboardExpand all lines: docs/ide/file-nesting-solution-explorer.md
+5-4Lines changed: 5 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,9 @@ author: angelosp
9
9
ms.author: angelpe
10
10
manager: jillfra
11
11
---
12
-
# Customize file nesting in Solution Explorer
12
+
# File nesting in Solution Explorer
13
13
14
-
Nesting of related files in **Solution Explorer** is not new, but until now you had no control over the nesting rules. You can choose between the presets **Off**, **Default** and **Web**, but you can also customize the nesting exactly to your liking. You can even create solution-specific and project-specific settings, but more on all of that later. First let’s go over what you get out-of-the-box.
14
+
**Solution Explorer** nests related files to help organize them and make them easier to locate. For example, if you add a Windows Forms form to a project, the code file for the form is nested below the form in **Solution Explorer**. In ASP.NET Core projects, file nesting can be taken a step further. You can choose between the file nesting presets **Off**, **Default**, and **Web**. You can also [customize how files are nested](#customize-file-nesting) or [create solution-specific and project-specific settings](#create-project-specific-settings).
15
15
16
16
> [!NOTE]
17
17
> The feature is currently only supported for ASP.NET Core projects.
@@ -122,7 +122,7 @@ You can manage all settings, including your own custom settings, through the sam
## Create solution-specific and project-specific settings
125
+
## Create project-specific settings
126
126
127
127
You can create solution-specific and project-specific settings through the right-click menu (context menu) of each solution and project:
128
128
@@ -136,7 +136,7 @@ You can do the opposite and tell Visual Studio to *only* use the solution-specif
136
136
137
137
Solution-specific and project-specific settings can be checked into source control, and the entire team that works on the codebase can share them.
138
138
139
-
## Disable global file nesting rules for a particular solution or project
139
+
## Disable file nesting rules for a project
140
140
141
141
You can disable existing global file nesting rules for specific solutions or projects by using the **remove** action for a provider instead of **add**. For example, if you add the following settings code to a project, all **pathSegment** rules that may exist globally for this specific project are disabled:
142
142
@@ -151,3 +151,4 @@ You can disable existing global file nesting rules for specific solutions or pro
151
151
## See also
152
152
153
153
-[Personalize the IDE](../ide/personalizing-the-visual-studio-ide.md)
154
+
-[Solutions and projects in Visual Studio](solutions-and-projects-in-visual-studio.md)
Copy file name to clipboardExpand all lines: docs/ide/reference/edit-devenv-exe.md
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -39,6 +39,8 @@ When a file isn't specified, an existing Visual Studio instance receives focus.
39
39
40
40
If the existing Visual Studio instance is in a modal state, the file opens in the existing instance when Visual Studio exits the modal state. For example, this situation may occur when the [Options dialog box](../../ide/reference/options-dialog-box-visual-studio.md) is open.
41
41
42
+
If more than one instance of Visual Studio is open, the file is opened in the most recently opened instance.
43
+
42
44
## Example
43
45
44
46
The first example opens the file `MyFile.cs` in an existing instance of Visual Studio. If a Visual Studio instance doesn't exist, the tool opens the file in a new instance. The second example is similar except that it opens three files instead of just one file.
Copy file name to clipboardExpand all lines: docs/ide/solutions-and-projects-in-visual-studio.md
+12-11Lines changed: 12 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -3,20 +3,17 @@ title: Solutions and projects
3
3
ms.date: 10/05/2017
4
4
ms.topic: conceptual
5
5
f1_keywords:
6
+
- "vs.addnewitem"
6
7
- "vs.addnewsolutionitem"
7
-
- "vs.environment.projects"
8
8
- "vs.openproject"
9
-
- "vs.addnewitem"
10
9
- "vs.addexistingitem"
11
-
- "VS.SolutionExplorer"
12
10
- "vs.addexistingsolutionitem"
11
+
- "vs.environment.projects"
13
12
- "vs.environment.solutions"
13
+
- "VS.SolutionExplorer"
14
14
- "VS.SolutionExplorer.Solutions"
15
15
helpviewer_keywords:
16
-
- "solution items [Visual Studio]"
17
16
- "solutions [Visual Studio]"
18
-
- "project items [Visual Studio]"
19
-
- "solutions [Visual Studio], designing"
20
17
- "projects [Visual Studio]"
21
18
author: gewarren
22
19
ms.author: gewarren
@@ -58,18 +55,22 @@ Visual Studio uses two file types (*.sln* and *.suo*) to store settings for solu
58
55
59
56
## Create new projects
60
57
61
-
The easiest way to create a new project is to start from a project template for a particular type of application or website. A project template consists of a basic set of pre-generated code files, config files, assets, and settings. These templates are available in the dialog box where you create a new project (**File** > **New** > **Project**). For more information, see [Create solutions and projects](../ide/creating-solutions-and-projects.md).
58
+
The easiest way to create a new project is to start from a project template for a particular type of application or website. A project template consists of a basic set of pre-generated code files, config files, assets, and settings. These templates are available in the dialog box where you create a new project (**File** > **New** > **Project**). For more information, see [Create a new project in Visual Studio](create-new-project.md) and [Create solutions and projects](../ide/creating-solutions-and-projects.md).
62
59
63
-
You can also create custom project and item templates. For more information, see [Create project and item templates](../ide/creating-project-and-item-templates.md).
60
+
If you often customize your projects in a certain way, You can create a custom project template that you can then use to create new projects from. For more information, see [Create project and item templates](../ide/creating-project-and-item-templates.md).
64
61
65
-
When you create a new project, it is saved by default at *%USERPROFILE%\source\repos*. You can customize this location in the **Projects location** setting under **Tools** > **Options** > **Projects and Solutions** > **Locations**. For more information, see [Projects and Solutions page, Options dialog box](../ide/reference/projects-and-solutions-options-dialog-box.md).
62
+
When you create a new project, it is saved by default at *%USERPROFILE%\source\repos*. You can change this location in the **Projects location** setting under **Tools** > **Options** > **Projects and Solutions** > **Locations**. For more information, see [Projects and Solutions page, Options dialog box](../ide/reference/projects-and-solutions-options-dialog-box.md).
66
63
67
-
## Manage projects in Solution Explorer
64
+
## Solution Explorer
68
65
69
-
After you create a new project, you can use **Solution Explorer** to view and manage the project and solution, and their associated items. The following illustration shows **Solution Explorer** with a C# solution that contains two projects:
66
+
After you create a new project, you can use **Solution Explorer** to view and manage the project and solution and their associated items. The following illustration shows **Solution Explorer** with a C# solution that contains two projects:
Many menu commands are available from the right-click menu on various items in **Solution Explorer**. These commands include building a project, managing NuGet packages, adding a reference, renaming a file, and running tests, just to name a few. The toolbar across the top of **Solution Explorer** has buttons to switch from a solution view to a folder view, show hidden files, collapse all nodes, and more.
71
+
72
+
For ASP.NET Core projects, you can customize how files are nested in **Solution Explorer**. For more information, see [Customize file nesting in Solution Explorer](file-nesting-solution-explorer.md).
73
+
73
74
## See also
74
75
75
76
-[Visual Studio IDE](../get-started/visual-studio-ide.md)
0 commit comments