Update documents to preview 7 version (#401)

diff --git a/documentation/dotnet-counters-instructions.md b/documentation/dotnet-counters-instructions.md
index 75e96a0c3616e601c1b75847b5e55c9df1969753..2c515631335469f116444307d3492ced8dd9c7db 100644 (file)
--- a/documentation/dotnet-counters-instructions.md
+++ b/documentation/dotnet-counters-instructions.md
@@ -9,7 +9,7 @@ dotnet-counters is a performance monitoring tool for ad-hoc health monitoring or
 ## Install dotnet-counters
 
 ```
-dotnet tool install --global dotnet-counters --version 1.0.4-preview6.19311.1
+dotnet tool install --global dotnet-counters --version 3.0.0-preview7.19365.2
 ```
 
 

diff --git a/documentation/dotnet-dump-instructions.md b/documentation/dotnet-dump-instructions.md
index 5115a946868f15061b8e0f9a3cdea614e00d2a58..9a8db7e54f677c690f9d86e0af679db57b1ba89e 100644 (file)
--- a/documentation/dotnet-dump-instructions.md
+++ b/documentation/dotnet-dump-instructions.md
@@ -9,9 +9,9 @@ Currently not supported on macOS.
 
 The first step is to install the dotnet-dump CLI global tool. This requires at least the 2.1 or greater .NET Core SDK to be installed. If you see the error message `Tool 'dotnet-dump' is already installed`, you will need to uninstall the global tool (see below). 
 
-    $ dotnet tool install -g dotnet-dump --version 1.0.4-preview6.19311.1
+    $ dotnet tool install -g dotnet-dump --version 3.0.0-preview7.19365.2
     You can invoke the tool using the following command: dotnet-dump
-    Tool 'dotnet-dump' (version '1.0.4-preview6.19311.1') was successfully installed.
+    Tool 'dotnet-dump' (version '3.0.0-preview7.19365.2') was successfully installed.
 
 If this is the first global tool installed or you get message `Could not execute because the specified command or file was not found.` you need to add `$HOME/.dotnet/tools` to your path.
 
@@ -118,4 +118,4 @@ This command on Microsoft .NET Core SDK Linux docker images can throw `Unhandled
 ## Uninstalling dotnet-dump 
 
     $ dotnet tool uninstall -g dotnet-dump
-    Tool 'dotnet-dump' (version '1.0.4-preview6.19311.1') was successfully uninstalled.
+    Tool 'dotnet-dump' (version '3.0.0-preview7.19365.2') was successfully uninstalled.

diff --git a/documentation/dotnet-trace-instructions.md b/documentation/dotnet-trace-instructions.md
index ec63eb6ec462492aa346fc8ecddd0a408eebeec4..7803ee5d162555f5790966446a54dd2701691721 100644 (file)
--- a/documentation/dotnet-trace-instructions.md
+++ b/documentation/dotnet-trace-instructions.md
@@ -7,9 +7,9 @@ The dotnet-trace tool is a cross-platform CLI global tool that enables the colle
 The first step is to install the dotnet-trace CLI global tool.
 
 ```cmd
-$ dotnet tool install --global dotnet-trace --version 1.0.4-preview6.19311.1
+$ dotnet tool install --global dotnet-trace --version 3.0.0-preview7.19365.2
 You can invoke the tool using the following command: dotnet-trace
-Tool 'dotnet-trace' (version '1.0.4-preview6.19311.1') was successfully installed.
+Tool 'dotnet-trace' (version '3.0.0-preview7.19365.2') was successfully installed.
 ```
 
 ## Using dotnet-trace

diff --git a/documentation/installing-sos-instructions.md b/documentation/installing-sos-instructions.md
index 9a92a5a478511914f1183273f426004223a2e133..2286041a5ef99b83185f27a21f51cdc2bee16f01 100644 (file)
--- a/documentation/installing-sos-instructions.md
+++ b/documentation/installing-sos-instructions.md
@@ -3,14 +3,14 @@ Installing SOS on Linux and MacOS
 
 The first step is to install the dotnet-sos CLI global tool. This requires at least the 2.1 or greater .NET Core SDK to be installed. If you see the error message `Tool 'dotnet-sos' is already installed`, you will need to uninstall the global tool (see below). 
 
-    $ dotnet tool install -g dotnet-sos --version 1.0.4-preview6.19311.1
+    $ dotnet tool install -g dotnet-sos --version 3.0.0-preview7.19365.2
     You can invoke the tool using the following command: dotnet-sos
-    Tool 'dotnet-sos' (version '1.0.4-preview6.19311.1') was successfully installed.
+    Tool 'dotnet-sos' (version '3.0.0-preview7.19365.2') was successfully installed.
 
 The next step is use this global tool to install SOS. 
 
     $ dotnet-sos install
-    Installing SOS to /home/mikem/.dotnet/sos from /home/mikem/.dotnet/tools/.store/dotnet-sos/1.0.4-preview6.19311.1/dotnet-sos/1.0.4-preview6.19311.1/tools/netcoreapp2.1/any/linux-x64
+    Installing SOS to /home/mikem/.dotnet/sos from /home/mikem/.dotnet/tools/.store/dotnet-sos/3.0.0-preview7.19365.2/dotnet-sos/3.0.0-preview7.19365.2/tools/netcoreapp2.1/any/linux-x64
     Creating installation directory...
     Copying files...
     Updating existing /home/mikem/.lldbinit file - LLDB will load SOS automatically at startup
@@ -72,7 +72,7 @@ Now any time you run lldb, SOS will automatically be loaded and the symbol downl
 The installer needs to be run again:
 
     $ dotnet-sos install
-    Installing SOS to /home/mikem/.dotnet/sos from /home/mikem/.dotnet/tools/.store/dotnet-sos/1.0.4-preview6.19311.1/dotnet-sos/1.0.4-preview6.19311.1/tools/netcoreapp2.1/any/linux-x64
+    Installing SOS to /home/mikem/.dotnet/sos from /home/mikem/.dotnet/tools/.store/dotnet-sos/3.0.0-preview7.19365.2/dotnet-sos/3.0.0-preview7.19365.2/tools/netcoreapp2.1/any/linux-x64
     Installing over existing installation...
     Creating installation directory...
     Copying files...
@@ -92,4 +92,4 @@ To uninstall and remove the lldb configuration run this command:
 To remove the SOS installer global tool:
 
     $ dotnet tool uninstall -g dotnet-sos
-    Tool 'dotnet-sos' (version '1.0.4-preview6.19311.1') was successfully uninstalled.
+    Tool 'dotnet-sos' (version '3.0.0-preview7.19365.2') was successfully uninstalled.

diff --git a/documentation/installing-sos-windows-instructions.md b/documentation/installing-sos-windows-instructions.md
index 7f6452834e3cba66d25d9adb33ed7c9c58caf38b..fffd19d061aad6b85e5177ba406d94df462c25f1 100644 (file)
--- a/documentation/installing-sos-windows-instructions.md
+++ b/documentation/installing-sos-windows-instructions.md
@@ -47,14 +47,14 @@ SOS will automatically be loaded from the internal Microsoft extension gallery.
 
 It is recommended that you update to the newer versions of the Windows debugger, but you can still use the latest SOS with older Windows debuggers by using the dotnet-sos CLI global tool to install. It is not as convenient. You may have to ".unload" the SOS that is loaded from the "runtime" directory.
 
-    C:\Users\mikem>dotnet tool install -g dotnet-sos --version 1.0.4-preview6.19311.1
+    C:\Users\mikem>dotnet tool install -g dotnet-sos --version 3.0.0-preview7.19365.2
     You can invoke the tool using the following command: dotnet-sos
-    Tool 'dotnet-sos' (version '1.0.4-preview6.19311.1') was successfully installed.
+    Tool 'dotnet-sos' (version '3.0.0-preview7.19365.2') was successfully installed.
 
 Run the installer:
 
     C:\Users\mikem>dotnet-sos install
-    Installing SOS to C:\Users\mikem\.dotnet\sos from C:\Users\mikem\.dotnet\tools\.store\dotnet-sos\1.0.4-preview6.19311.1\dotnet-sos\1.0.4-preview6.19311.1\tools\netcoreapp2.1\any\win-x64
+    Installing SOS to C:\Users\mikem\.dotnet\sos from C:\Users\mikem\.dotnet\tools\.store\dotnet-sos\3.0.0-preview7.19365.2\dotnet-sos\3.0.0-preview7.19365.2\tools\netcoreapp2.1\any\win-x64
     Creating installation directory...
     Copying files...
     Execute '.load C:\Users\mikem\.dotnet\sos\sos.dll' to load SOS in your Windows debugger.

diff --git a/documentation/tutorial/installing_the_diagnostics_tools.md b/documentation/tutorial/installing_the_diagnostics_tools.md
index 450e344ac407762138d1aefaff885e16b7e1243e..9ef283e3e2af9f3dc26da383425ec95b7913e511 100644 (file)
--- a/documentation/tutorial/installing_the_diagnostics_tools.md
+++ b/documentation/tutorial/installing_the_diagnostics_tools.md
@@ -6,7 +6,7 @@ Depending on the diagnostics scenario you will use one or more of the tools belo
 In the .NET full/Windows world, we have a myriad of performance counters that can be used to triage and diagnose production issues. For .Net core we have a similar and cross platform story centered around a tool called dotnet-counters. To install the tool, run the following command:
 
 > ```bash
-> dotnet tool install --global dotnet-counters --version 1.0.4-preview6.19311.1
+> dotnet tool install --global dotnet-counters --version 3.0.0-preview7.19365.2
 > ```
 
 
@@ -14,7 +14,7 @@ In the .NET full/Windows world, we have a myriad of performance counters that ca
 .NET core includes what is called the 'EventPipe' through which diagnostics data is exposed. The dotnet-trace tool allows you to consume interesting profiling data from your app that can help in scenarios where you need to root cause apps running slow. To install the tool, run the following command:
 
 > ```bash
-> dotnet tool install --global dotnet-trace --version 1.0.4-preview6.19311.1 
+> dotnet tool install --global dotnet-trace --version 3.0.0-preview7.19365.2 
 > ```
 
 
@@ -22,7 +22,7 @@ In the .NET full/Windows world, we have a myriad of performance counters that ca
 In order to generate core dumps for .net core apps, you can use the dotnet-dump tool. To install the tool, run the following command:
 
 > ```bash
-> dotnet tool install --global dotnet-dump --version 1.0.4-preview6.19311.1
+> dotnet tool install --global dotnet-dump --version 3.0.0-preview7.19365.2
 > ```