Explicitly mention need for nuget.exe.
...which, oddly, is not included in Visual Studio.
Bob Arnson committed
Mar 30, 2023 at 17:11 UTC
af72e6fdc0b2ba81bdacf2a460faf01c24b1e220
1 file changed
+6
-4
README.md
+6
-4
@@ -12,7 +12,7 @@ This repository contains the WiX Toolset v4 codebase.
12
13
## Prerequisites
14
15
-Visual Studio 2022 (17.0.4 or higher) with the following installed:
15
+- Visual Studio 2022 (17.0.4 or higher) with the following installed:
16
17
| Workloads |
18
| :-------- |
@@ -29,6 +29,8 @@ Visual Studio 2022 (17.0.4 or higher) with the following installed:
29
| MSVC v143 - VS 2022 C++ ARM64 build tools (Latest) |
30
| MSVC v143 - VS 2022 C++ x64/x86 build tools (Latest) |
31
32
+- [Download the latest nuget.exe command-line tool](https://www.nuget.org/downloads) and put it in a directory on the path.
33
+
34
##### Getting started:
35
36
* Fork the WiX4 repository (https://github.com/wixtoolset/wix4.git)
@@ -43,11 +45,11 @@ Visual Studio 2022 (17.0.4 or higher) with the following installed:
45
* Issue the command `devbuild` (or `devbuild release` if you want to create a release version)
46
47
##### Executing your newly built WiX toolset
46
-
48
+
49
* `build\wix\Debug\publish\wix\wix --help` (Of course changing Debug to Release if you built in Release mode)
50
51
##### Pull request expectations
50
-
52
+
53
* Pick an outstanding WiX4 issue (or create one). Add a comment requesting that you be assigned to the issue. Wait for confirmation.
54
* To create a PR fork a new branch from the develop branch
55
* Make changes to effect whatever changed behaviour is required for the PR
@@ -56,4 +58,4 @@ Visual Studio 2022 (17.0.4 or higher) with the following installed:
58
* If the develop branch has changed since you created your new branch rebase to the current development branch.
59
* If needed (ie, you squashed or rebased), do a force push of your branch
60
* Create a PR with your branch against the WiX4 repository.
59
-
61
+