Update to Preview 6 version: 1.0.4-preview6.19311.1

diff --git a/documentation/dotnet-counters-instructions.md b/documentation/dotnet-counters-instructions.md
index 3277e2b4b8b7b0804af72849931a0800f6829554..7872001554aa5900745e3cdbd8098bd8689cea9e 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.3-preview5.19251.2
+dotnet tool install --global dotnet-counters --version 1.0.4-preview6.19311.1
 ```
 
 

diff --git a/documentation/dotnet-dump-instructions.md b/documentation/dotnet-dump-instructions.md
index e62aadb5eeb7a8169430dca027698d8536ae23a9..eb7fd9c508d65a38fa4b0e079062ffe652e40e96 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.3-preview5.19251.2
+    $ dotnet tool install -g dotnet-dump --version 1.0.4-preview6.19311.1
     You can invoke the tool using the following command: dotnet-dump
-    Tool 'dotnet-dump' (version '1.0.3-preview5.19251.2') was successfully installed.
+    Tool 'dotnet-dump' (version '1.0.4-preview6.19311.1') 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.3-preview5.19251.2') was successfully uninstalled.
+    Tool 'dotnet-dump' (version '1.0.4-preview6.19311.1') was successfully uninstalled.

diff --git a/documentation/dotnet-trace-instructions.md b/documentation/dotnet-trace-instructions.md
index 849050694af40e863bf28a3cbd21f5e35b68b2c7..6b4eade5c273affa2883e48d13c7ac8ace0d33cf 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. This requires at least version 2.1 of the SDK to be installed.
 
 ```cmd
-$ dotnet tool install --global dotnet-trace --version 1.0.3-preview5.19251.2
+$ dotnet tool install --global dotnet-trace --version 1.0.4-preview6.19311.1
 You can invoke the tool using the following command: dotnet-trace
-Tool 'dotnet-trace' (version '1.0.3-preview5.19251.2') was successfully installed.
+Tool 'dotnet-trace' (version '1.0.4-preview6.19311.1') was successfully installed.
 ```
 
 ## Using dotnet-trace

diff --git a/documentation/installing-sos-instructions.md b/documentation/installing-sos-instructions.md
index ff8921e1d6f1e38d6d6d4455e3a24d8cd6ae5aec..62c0fb41d3a1568d00e7009e3700d5c6d8ba7081 100644 (file)
--- a/documentation/installing-sos-instructions.md
+++ b/documentation/installing-sos-instructions.md
@@ -3,16 +3,16 @@ 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.3-preview5.19251.2
+    $ dotnet tool install -g dotnet-sos --version 1.0.4-preview6.19311.1
     You can invoke the tool using the following command: dotnet-sos
-    Tool 'dotnet-sos' (version '1.0.3-preview5.19251.2') was successfully installed.
+    Tool 'dotnet-sos' (version '1.0.4-preview6.19311.1') 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.3-preview5.19251.2/dotnet-sos/1.0.3-preview5.19251.2/tools/netcoreapp2.1/any/linux-x64
+    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
     Creating installation directory...
     Copying files...
     Updating existing /home/mikem/.lldbinit file - LLDB will load SOS automatically at startup
@@ -74,7 +74,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.3-preview5.19251.2/dotnet-sos/1.0.3-preview5.19251.2/tools/netcoreapp2.1/any/linux-x64
+    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 over existing installation...
     Creating installation directory...
     Copying files...
@@ -94,4 +94,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.3-preview5.19251.2') was successfully uninstalled.
+    Tool 'dotnet-sos' (version '1.0.4-preview6.19311.1') was successfully uninstalled.

diff --git a/documentation/installing-sos-windows-instructions.md b/documentation/installing-sos-windows-instructions.md
index 61ecd0f9042e5ee40297dc14216df37db8cb1b15..600ae5957c1448a1cf81f0f1e685489e3b77c05e 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.3-preview5.19251.2
+    C:\Users\mikem>dotnet tool install -g dotnet-sos --version 1.0.4-preview6.19311.1
     You can invoke the tool using the following command: dotnet-sos
-    Tool 'dotnet-sos' (version '1.0.3-preview5.19251.2') was successfully installed.
+    Tool 'dotnet-sos' (version '1.0.4-preview6.19311.1') 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.3-preview5.19251.2\dotnet-sos\1.0.3-preview5.19251.2\tools\netcoreapp2.1\any\win-x64
+    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
     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 4c5589c6ea0710e3b52b16efb6ee0227331964fb..df315f2b6c74a3cfe75e2c8bf71b986827b5b9c2 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.3-preview5.19251.2
+> dotnet tool install --global dotnet-counters --version 1.0.4-preview6.19311.1
 > ```
 
 
@@ -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.3-preview5.19251.2 
+> dotnet tool install --global dotnet-trace --version 1.0.4-preview6.19311.1 
 > ```
 
 Please note, the dotnet-trace tool is version independent but as of right now (preview 5) it requires the 2.1 runtime to be installed to work. This will be fixed moving forward.
@@ -24,7 +24,7 @@ Please note, the dotnet-trace tool is version independent but as of right now (p
 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.3-preview5.19251.2
+> dotnet tool install --global dotnet-dump --version 1.0.4-preview6.19311.1
 > ```
 
 Please note, the dotnet-trace tool is version independent but as of right now (preview 5) it requires the 2.1 runtime to be installed to work. This will be fixed moving forward.