Skip to content

Commit 42b2554

Browse files
committed
better links
1 parent c8c2ec0 commit 42b2554

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/vs-2015/profiling/concurrency-visualizer-sdk.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ manager: jillfra
1515
# Concurrency Visualizer SDK
1616
[!INCLUDE[vs2017banner](../includes/vs2017banner.md)]
1717

18-
You can instrument your source code by using the Concurrency Visualizer SDK to display additional information in the Concurrency Visualizer. You can associate the additional data with phases and events in your code. These additional visualizations are known as *markers*. For an introductory walkthrough, see [Introducing the Concurrency Visualizer SDK](https://blogs.msdn.microsoft.com/visualizeparallel/2011/10/17/introducing-the-concurrency-visualizer-sdk/).
18+
You can instrument your source code by using the Concurrency Visualizer SDK to display additional information in the Concurrency Visualizer. You can associate the additional data with phases and events in your code. These additional visualizations are known as *markers*. For an introductory walkthrough, see [Introducing the Concurrency Visualizer SDK](https://docs.microsoft.com/archive/blogs/visualizeparallel/introducing-the-concurrency-visualizer-sdk).
1919

2020
## Properties
2121
Flags, spans, and messages each have two properties: category and importance. In the [Advanced Settings](../profiling/advanced-settings-dialog-box-concurrency-visualizer.md) dialog box, you can use these properties to filter the set of markers that are displayed. In addition, these properties affect the visual representation of markers. For example, the size of flags is used to represent importance. In addition, color is used to indicate category.

docs/vs-2015/profiling/concurrency-visualizer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ NOTE]
4343
|[Threads View](../profiling/threads-view-parallel-performance.md)|Describes how to analyze the interactions between threads in your program.|
4444
|[Cores View](../profiling/cores-view.md)|Describes how to analyze thread migration across cores.|
4545
|[Common Patterns for Poorly-Behaved Multithreaded Applications](../profiling/common-patterns-for-poorly-behaved-multithreaded-applications.md)|Describes several common patterns and shows how they appear in the Concurrency Visualizer.|
46-
|[Parallel Development in Visual Studio blog](https://blogs.msdn.microsoft.com/visualizeparallel/)|Provides tips and best practices for the Concurrency Visualizer.|
46+
|[Parallel Development in Visual Studio blog](https://docs.microsoft.com/archive/blogs/visualizeparallel/)|Provides tips and best practices for the Concurrency Visualizer.|
4747
|[Performance Report Views](../profiling/performance-report-views.md)|Provides reference information for the reports and views of Visual Studio Profiling Tools.|
4848
|[Concurrency Visualizer SDK](../profiling/concurrency-visualizer-sdk.md)|Describes how to instrument your source code to display additional information in the Concurrency Visualizer.|
4949
|[Concurrency Visualizer Command-Line Utility (CVCollectionCmd)](../profiling/concurrency-visualizer-command-line-utility-cvcollectioncmd.md)|Describes how to use the Concurrency Visualizer command line utility (CVCollectionCmd.exe) to collect and process traces on machines that don't have Visual Studio.|

0 commit comments

Comments
 (0)