Merge pull request #1968 from dotnet/stevesa/update-mono-2020-02-03

Update Mono

UpgradeMono.ps1

@@ -31,6 +31,7 @@ $outputBclFacadesDir = Join-Path -Path $outputBclDir -ChildPath Facades
 $outputFrameworkDir = Join-Path -Path $outputRoot -ChildPath framework
 $outputLinkerDir = Join-Path -Path $outputRoot -ChildPath "..\tools\binaries\monolinker"
 
+Write-Host "Copying in new Mono binaries from '$MonoRootDir'..."
 New-Item -Force -ItemType "directory" $outputWasmDir | Out-Null
 Copy-Item "$inputWasmDir\dotnet.wasm" -Destination $outputWasmDir
 Copy-Item "$inputWasmDir\dotnet.js" -Destination $outputWasmDir

src/Microsoft.AspNetCore.Blazor.Mono/HowToUpgradeMono.md

@@ -29,7 +29,7 @@ All this script does is remove older binaries from the `incoming` and `tools` di
 
 Verify that there were no errors, and that resulting git diff looks reasonable. For normal upgrades, you should see:
 
- * `mono.js` and `mono.wasm` have been modified
+ * `dotnet.js` and `dotnet.wasm` have been modified
  * Many of the .NET assemblies in `bcl` and `bcl\facades` have been modified. Occasionally some new ones will be added, or some may be removed, though this is quite unusual.
  * The three .NET assemblies in `framework` will usually have been modified. It's not expected for assemblies to be added or removed here, so check with Mono if that seems to have happened.
  * The linker binaries in `tools` will usually have been modified.