Update docs to Preview 9 version (#460)

diff --git a/documentation/dotnet-counters-instructions.md b/documentation/dotnet-counters-instructions.md
index 792f94178d876e7485ebb2e7158b11ebb9aacd51..57d3c75c0baf6ae0b6023ee3de326d2f850d5248 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 3.0.0-preview8.19412.1
+dotnet tool install --global dotnet-counters --version 3.0.0-preview9.19454.1
 ```
 
 

diff --git a/documentation/dotnet-dump-instructions.md b/documentation/dotnet-dump-instructions.md
index 77ccff9b74d7c23e1ab03ad671bbe5397ad05492..678a1572dc7907327ea312688d255e1668417abf 100644 (file)
--- a/documentation/dotnet-dump-instructions.md
+++ b/documentation/dotnet-dump-instructions.md
@@ -1,7 +1,7 @@
 Dump collection and analysis utility (dotnet-dump)
 ==================================================
 
-The dotnet-dump CLI global tool is way to collect and analyze Windows and Linux dumps all without any native debugger involved like lldb on Linux. This is important on platforms like Alpine Linux where a fully working lldb isn't available. The dotnet-dump tool will allow you to run SOS commands to analyze crashes and the GC, but it isn't a native debugger so things like displaying the native stack frames isn't supported.
+The dotnet-dump CLI global tool is way to collect and analyze Windows and Linux dumps all without any native debugger involved like lldb on Linux. This is important on platforms like Alpine Linux or Linux ARM32/ARM64 where a fully working lldb isn't available. The dotnet-dump tool will allow you to run SOS commands to analyze crashes and the GC, but it isn't a native debugger so things like displaying the native stack frames isn't supported.
 
 Currently not supported on macOS.
 
@@ -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 3.0.0-preview8.19412.1
+    $ dotnet tool install -g dotnet-dump --version 3.0.0-preview9.19454.1
     You can invoke the tool using the following command: dotnet-dump
-    Tool 'dotnet-dump' (version '3.0.0-preview8.19412.1') was successfully installed.
+    Tool 'dotnet-dump' (version '3.0.0-preview9.19454.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 '3.0.0-preview8.19412.1') was successfully uninstalled.
+    Tool 'dotnet-dump' (version '3.0.0-preview9.19454.1') was successfully uninstalled.

diff --git a/documentation/dotnet-trace-instructions.md b/documentation/dotnet-trace-instructions.md
index f43beacd5151db26bc7323f2457344a97963a44f..938086be501910f3f1d99cd6b979a3a994f88dc2 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 3.0.0-preview8.19412.1
+$ dotnet tool install --global dotnet-trace --version 3.0.0-preview9.19454.1
 You can invoke the tool using the following command: dotnet-trace
-Tool 'dotnet-trace' (version '3.0.0-preview8.19412.1') was successfully installed.
+Tool 'dotnet-trace' (version '3.0.0-preview9.19454.1') was successfully installed.
 ```
 
 ## Using dotnet-trace

diff --git a/documentation/installing-sos-instructions.md b/documentation/installing-sos-instructions.md
index df9097579aa35d2436fa2b2f855c65b3bec1e4fd..e5576ab62b9f2a6e2d5a5575edcfe4828de8d2e1 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 3.0.0-preview8.19412.1
+    $ dotnet tool install -g dotnet-sos --version 3.0.0-preview9.19454.1
     You can invoke the tool using the following command: dotnet-sos
-    Tool 'dotnet-sos' (version '3.0.0-preview8.19412.1') was successfully installed.
+    Tool 'dotnet-sos' (version '3.0.0-preview9.19454.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/3.0.0-preview8.19412.1/dotnet-sos/3.0.0-preview8.19412.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-preview9.19454.1/dotnet-sos/3.0.0-preview9.19454.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
@@ -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/3.0.0-preview8.19412.1/dotnet-sos/3.0.0-preview8.19412.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-preview9.19454.1/dotnet-sos/3.0.0-preview9.19454.1/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 '3.0.0-preview8.19412.1') was successfully uninstalled.
+    Tool 'dotnet-sos' (version '3.0.0-preview9.19454.1') was successfully uninstalled.

diff --git a/documentation/installing-sos-windows-instructions.md b/documentation/installing-sos-windows-instructions.md
index d1a4ea8083af814380d6ff966b756b7f4911efa3..39764429b76a3860bab0d66b65083c78a1c9b9c2 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 3.0.0-preview8.19412.1
+    C:\Users\mikem>dotnet tool install -g dotnet-sos --version 3.0.0-preview9.19454.1
     You can invoke the tool using the following command: dotnet-sos
-    Tool 'dotnet-sos' (version '3.0.0-preview8.19412.1') was successfully installed.
+    Tool 'dotnet-sos' (version '3.0.0-preview9.19454.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\3.0.0-preview8.19412.1\dotnet-sos\3.0.0-preview8.19412.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-preview9.19454.1\dotnet-sos\3.0.0-preview9.19454.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 8f9562c85ff4465f3585524de50612d3d979408e..aa8d72e08893139c310a2a142eaded7a86c72253 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 3.0.0-preview8.19412.1
+> dotnet tool install --global dotnet-counters --version 3.0.0-preview9.19454.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 3.0.0-preview8.19412.1 
+> dotnet tool install --global dotnet-trace --version 3.0.0-preview9.19454.1 
 > ```
 
 
@@ -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 3.0.0-preview8.19412.1
+> dotnet tool install --global dotnet-dump --version 3.0.0-preview9.19454.1
 > ```