Document how to update dependencies and use local changes.

1 files changed, 24 insertions, 1 deletions

diff --git a/README.md b/README.md
index 431f7b9c..8cfb9437 100644
--- a/README.md
+++ b/README.md
@@ -22,4 +22,27 @@ For example, the following line runs only the specified test:
 The VM must have:
 1. x64 .NET Core SDK of 5.0 or later (for the test runner)
 1. Any version of .NET Framework (for the .NET Framework TestBA)
-1. x86 .NET Core Desktop Runtime of 5.0 or later (for the .NET Core TestBA)
\ No newline at end of file
+1. x86 .NET Core Desktop Runtime of 5.0 or later (for the .NET Core TestBA)
+
+## Updating dependencies
+
+Use the `updatepackage.ps1` script from https://github.com/wixtoolset/Home.
+For example:
+
+* updatepackage.ps1 -TargetFolder path\to\repo -PackageName WixToolset.Bal.wixext -NewVersion 4.0.80
+* updatepackage.ps1 -TargetFolder path\to\repo -PackageName WixToolset.Mba.Core -NewVersion 4.0.45
+* updatepackage.ps1 -TargetFolder path\to\repo -PackageName WixToolset.NetFx.wixext -NewVersion 4.0.57
+* updatepackage.ps1 -TargetFolder path\to\repo -PackageName WixToolset.Util.wixext -NewVersion 4.0.67
+* updatepackage.ps1 -TargetFolder path\to\repo -PackageName WixToolset.Sdk -NewVersion 4.0.0-build-0176
+
+## Building with local changes
+
+The micro repo model makes this very difficult and painful.
+The basic idea is to make your changes in each individual repo on the master branch (to get a stable version), commit, and then use appveyor.cmd to build the nuget package.
+Put your custom nuget packages into a folder, and modify each repo's nuget.config with an entry to that folder.
+
+Alternatively, go into the NuGet package cache (%USERPROFILE%\.nuget\packages) and replace the official binaries with your locally built binaries.
+
+Both of those approaches will poison your NuGet package cache, so you probably will want to run the following command to clear it when you're done:
+
+> nuget locals all -clear
\ No newline at end of file