Skip to content

Commit ffea4dc

Browse files
committed
fixed #1877
1 parent d82af60 commit ffea4dc

File tree

2 files changed

+6
-4
lines changed

2 files changed

+6
-4
lines changed

docs/deployment/how-to-specify-a-start-menu-name-for-a-clickonce-application.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ When a [!INCLUDE[ndptecclick](../deployment/includes/ndptecclick_md.md)] applica
2626

2727
**Publisher name** will appear on the *publish.htm* page above **Product name**, and for an installed offline application, it will also be the name of the folder that contains the application's icon in the **Start** menu.
2828

29-
The Start menu shortcut or app reference is created in *%appdata%\Microsoft\Windows\Start Menu\Programs\<publisher name>* with the same name as the prouct name.
29+
The Start menu shortcut or app reference gets created in *%appdata%\Microsoft\Windows\Start Menu\Programs\\<publisher name\>*. The shortcut or app reference has the same name as the product name.
3030

3131
You can set the **Product name** and **Publisher name** properties in the **Publish Options** dialog box, available on the **Publish** page of the **Project Designer**.
3232

docs/profiling/walkthrough-using-profiler-apis.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,11 @@ The walkthrough uses a C# application to demonstrate how to use the [!INCLUDE[vs
2626

2727
The Visual Studio profiler allows you to limit the collection of data. This walkthrough offers an example of how to limit the collection of data by using the profiler APIs. The Visual Studio profiler provides an API for controlling data collection from within an application.
2828

29-
For native code, the Visual Studio profiler APIs are in *VSPerf.dll*. The header file, *VSPerf.h*, and the import library, *VSPerf.lib*, are located in the *Microsoft Visual Studio 9\Team Tools\Performance Tools* directory.
29+
For native code, the Visual Studio profiler APIs are in *VSPerf.dll*. The header file, *VSPerf.h*, and the import library, *VSPerf.lib*, are located in the *Microsoft Visual Studio\2017\Team Tools\Performance Tools\PerfSDK* directory. For 64-bit, the folder is *Microsoft Visual Studio\2017\Team Tools\Performance Tools\x64\PerfSDK*
30+
31+
For managed code, the profiler APIs are in the *Microsoft.VisualStudio.Profiler.dll*. This DLL is found in the *Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools* directory. For 64-bit, the folder is *Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools\x64*. For more information, see <xref:Microsoft.VisualStudio.Profiler>.
32+
3033

31-
For managed code, the profiler APIs are in the *Microsoft.VisualStudio.Profiler.dll*. This DLL is found in the *Microsoft Visual Studio 9\Team Tools\Performance Tools* directory. For more information, see <xref:Microsoft.VisualStudio.Profiler>.
3234

3335
## Prerequisites
3436
This walkthrough assumes your choice of development environment is configured to support debugging and sampling. The following topics provide an overview of these prerequisites:
@@ -54,7 +56,7 @@ DataCollection.CurrentId);
5456
1. Create a new C# project in Visual Studio, or use a command line build, depending on your preference.
5557

5658
> [!NOTE]
57-
> Your build must reference the *Microsoft.VisualStudio.Profiler.dll* library, located in the *Microsoft Visual Studio 9\Team Tools\Performance Tools* directory.
59+
> Your build must reference the *Microsoft.VisualStudio.Profiler.dll* library, located in the *Microsoft Visual Studio\Shared\Common\VSPerfCollectionTools* directory.
5860
5961
2. Copy and paste the following code into your project:
6062

0 commit comments

Comments
 (0)