Skip to content

Commit 3d3c598

Browse files
authored
Merge pull request #12947 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch main)
2 parents db1a03d + 2725ce8 commit 3d3c598

5 files changed

+21
-20
lines changed

docs/debugger/remote-debugging-azure-app-service.md

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ This article describes how to attach the Visual Studio debugger to an ASP.NET Co
2525

2626
## Enable remote debugging
2727

28-
Before you can debug this issue with Visual Studio, you must enable the remote debugging feature on the App Service. This setting will allow the Visual Studio debugger to connect to the main App Service web hosting process.
28+
Before you can debug this issue with Visual Studio, you must enable the remote debugging feature on the App Service. This setting allows the Visual Studio debugger to connect to the main App Service web hosting process.
2929

3030
1. Sign into your own [Azure portal](https://portal.azure.com/).
3131

@@ -45,16 +45,14 @@ Your app service instance now supports remote debugging through Visual Studio.
4545

4646
## Configure debugging settings
4747

48-
Make sure you have completed the following steps in Visual Studio before debugging an app in Azure to ensure success.
49-
50-
1. First, make sure you have successfully built your project at least one time. A successful build ensures the source code and any necessary compiled files are ready to go. If your application is running locally, make sure to stop the app.
48+
1. Build your app without errors. Stop your app if it's running locally.
5149

5250
> [!NOTE]
5351
> Make sure the state of your local code matches what was deployed to Azure. This ensures that the local symbol files and source code line up with the deployed app.
5452
5553
1. Select **Debug > Options** from the top Visual Studio menu. Ensure that **Enable Just My code** is *unchecked* (as shown below), and then select **OK**.
5654

57-
Changing this setting allows Visual Studio to debug the optimized code that was deployed to Azure using the necessary symbol files from your local bin folder. Symbol files are used by the debugger as a bridge between compiled, executing code and the source code in Visual Studio, which is why it's important that your local source code matched the deploy app.
55+
Changing this setting allows Visual Studio to debug the optimized code that was deployed to Azure using the necessary symbol files from your local bin folder. Symbol files are used by the debugger as a bridge between compiled, executing code and the source code in Visual Studio. Matching symbol files are required for remote debugging.
5856

5957
:::image type="content" source="../debugger/media/vs-2022/visual-studio-remote-debug-settings.png" alt-text="A screenshot of the Visual Studio debugging settings.":::
6058

@@ -70,14 +68,17 @@ Make sure you have completed the following steps in Visual Studio before debuggi
7068

7169
1. Locate and select the App Service instance you created in the previous step, and then choose **OK**.
7270

73-
1. The `w3wp.exe` process should appear in the list of available processes to connect to, which is the main process of the Azure App Service that hosts the deployed application. Select that process and then choose **Attach** in the bottom right to connect the Visual Studio debugger.
71+
1. The `w3wp.exe` process should appear in the list of available processes to connect to. `w3wp.exe` is the main process of the Azure App Service that hosts the deployed application. Select the `w3wp.exe` process and then choose **Attach** in the bottom right.
7472

7573
:::image type="content" source="../debugger/media/vs-2022/visual-studio-remote-debug-attach-to-process.png" alt-text="A screenshot of the attach to process features." lightbox="../debugger/media/vs-2022/visual-studio-remote-debug-attach-to-process.png":::
7674

77-
1. In a C# application file such as `Index.cshtml.cs`, set a breakpoint by clicking in the left margin. (Or, right-click and choose **Breakpoint** > **Insert breakpoint**.)
75+
1. In a C# application file such as `Index.cshtml.cs`, set a breakpoint by clicking in the left margin. Alternatively, right-click and choose **Breakpoint** > **Insert breakpoint**.
7876

79-
1. Take action in the web app to hit the breakpoint. If you're attached to the process but can't hit the breakpoint, make sure your publish profile in Visual Studio is set to a Debug configuration instead of a Release configuration.
77+
1. In the web app, navigate to the endpoint with the breakpoint. If you're attached to the process but can't hit the breakpoint, make sure your publish profile in Visual Studio is set to a Debug configuration instead of a Release configuration.
8078

81-
1. (Optional) you can also verify that Visual Studio has loaded the symbol files for your debugging session. Navigate to **Debug > Windows > Modules** to open the modules window. This window should indicate that the symbol files were successfully loaded after the **Just my code** configuration changes you made earlier.
79+
1. Optional: To verify that Visual Studio has loaded the symbol files for your debugging session. Navigate to **Debug > Windows > Modules** to open the modules window. This window indicates that the symbol files were successfully loaded after the **Just my code** configuration changes you made earlier.
8280

8381
:::image type="content" source="../debugger/media/vs-2022/visual-studio-symbol-files.png" alt-text="A screenshot of the symbol files window.":::
82+
83+
> [!NOTE]
84+
> For subsequent debugging of the app service, select the select **Debug** > **Reattach to w3wp.exe** or use the Shift+Alt+P hot keys.

docs/extensibility/dotnet-sign-cli-reference-vsix.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -159,37 +159,37 @@ dotnet tool install --global --add-source <path-to-folder> <tool-name> --version
159159
- Sign *contoso.vsix* with a certificate imported to the **user** certificate store:
160160

161161
```dotnetcli
162-
sign contoso.vsix -cfp 24D589...FB9523B36E -d "Constoso VSIX Signature" -u "http://www.contoso.com"
162+
sign code certificate-store contoso.vsix -cfp 24D589...FB9523B36E -d "Constoso VSIX Signature" -u "http://www.contoso.com"
163163
```
164164

165165
- Sign *contoso.vsix* with certificate *cert.pfx* (not password protected) using a SHA-512 fingerprint:
166166

167167
```dotnetcli
168-
sign contoso.vsix -cfp A87A6F...894559B981 -cfpa sha512 -cf D:\certificates\cert.pfx -d "Constoso VSIX Signature" -u "http://www.contoso.com"
168+
sign code certificate-store contoso.vsix -cfp A87A6F...894559B981 -cfpa sha512 -cf D:\certificates\cert.pfx -d "Constoso VSIX Signature" -u "http://www.contoso.com"
169169
```
170170

171171
- Sign *contoso.vsix* with certificate *cert.pfx* (password protected):
172172

173173
```dotnetcli
174-
sign contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -cf cert.pfx -p <password> -d "Constoso VSIX Signature" -u "http://www.contoso.com"
174+
sign code certificate-store contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -cf cert.pfx -p <password> -d "Constoso VSIX Signature" -u "http://www.contoso.com"
175175
```
176176

177177
- Sign multiple VSIX packages - *contoso.vsix* and *all .vsix files in the directory specified* with certificate *cert.pfx* (not password protected):
178178

179179
```dotnetcli
180-
sign *.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -cf cert.pfx -d "Constoso VSIX Signature" -u "http://www.contoso.com"
180+
sign code certificate-store *.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -cf cert.pfx -d "Constoso VSIX Signature" -u "http://www.contoso.com"
181181
```
182182

183183
- Sign *contoso.vsix* with a certificate stored in a secure USB drive.
184184

185185
```dotnetcli
186-
sign contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -d "Constoso VSIX Signature" -u "http://www.contoso.com"
186+
sign code certificate-store contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -d "Constoso VSIX Signature" -u "http://www.contoso.com"
187187
```
188188

189189
- Sign *contoso.vsix* with a certificate stored in a secure USB drive and accessed from the **machine** certificate store (-km option).
190190

191191
```dotnetcli
192-
sign contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -km -d "Constoso VSIX Signature" -u "http://www.contoso.com"
192+
sign code certificate-store contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -km -d "Constoso VSIX Signature" -u "http://www.contoso.com"
193193
```
194194

195195
> [!NOTE]
@@ -198,5 +198,5 @@ dotnet tool install --global --add-source <path-to-folder> <tool-name> --version
198198
- Sign *contoso.vsix* with a certificate stored in a secure USB drive specifying file digest algorithm (-fd), timestamp server (-t), and a custom output path (-o) for the signed VSIX.
199199

200200
```dotnetcli
201-
sign contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -d "Constoso VSIX Signature" -u "http://www.contoso.com" -t "http://timestamp.acs.microsoft.com/" -fd sha256 -o "ContosoSigned.vsix"
201+
sign code certificate-store contoso.vsix -s 24D58920B2D24D00A7DF07FB9523B36E -csp "Microsoft Software Key Storage Provider" -k "NuGetSigning 0B2D249223B36D00A7DF07FB95E24D58" -d "Constoso VSIX Signature" -u "http://www.contoso.com" -t "http://timestamp.acs.microsoft.com/" -fd sha256 -o "ContosoSigned.vsix"
202202
```

docs/ide/optimize-visual-studio-startup-time.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ If Visual Studio detects slow startup, a pop-up message appears, alerting you to
2626

2727
The dialog box lists the extensions and tools windows that are affecting startup performance. You can change extension and tool window settings to improve startup performance.
2828

29-
## <a name="extensions" />To change extension settings to improve startup, solution load, and typing performance
29+
## <a name="extensions"></a> To change extension settings to improve startup, solution load, and typing performance
3030

3131
1. Open the **Performance Manager** dialog box by choosing **Help** > **Visual Studio Performance Manager** from the menu bar.
3232

@@ -38,7 +38,7 @@ The dialog box lists the extensions and tools windows that are affecting startup
3838

3939
You can always re-enable the extension for future sessions by using the **Extension Manager** or the **Visual Studio Performance Manager** dialog box.
4040

41-
## <a name="tool-windows" />To change tool window settings to improve startup time
41+
## <a name="tool-windows"></a> To change tool window settings to improve startup time
4242

4343
1. Open the **Performance Manager** dialog box by choosing **Help** > **Visual Studio Performance Manager** from the menu bar.
4444

docs/ide/walkthrough-creating-a-multiple-computer-build-environment.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -280,7 +280,7 @@ If *vcvarsall.bat* runs successfully—that is, no error message is displayed—
280280

281281
- %windir%\Microsoft.NET\Framework64\v4.0.30319
282282

283-
## <a name="install-msbuild-to-gac" /> Install MSBuild assemblies to the Global Assembly Cache (GAC) on the build computer
283+
## <a name="install-msbuild-to-gac"></a> Install MSBuild assemblies to the Global Assembly Cache (GAC) on the build computer
284284

285285
MSBuild requires some additional assemblies to be installed to the GAC on the build computer.
286286

docs/modeling/analyze-and-model-your-architecture.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ Use domain-specific language to:
7272
Learn more:
7373
- [Modeling SDK for Visual Studio - Domain-Specific Languages](../modeling/modeling-sdk-for-visual-studio-domain-specific-languages.md)
7474

75-
## <a name="VersionSupport" />Edition support for architecture and modeling tools
75+
## <a name="VersionSupport"></a> Edition support for architecture and modeling tools
7676

7777
Visual Studio is available in several editions. Not all of these provide support for the architecture and modeling tools. The following table shows the availability of each tool.
7878

0 commit comments

Comments
 (0)