diff options
| author | LukePulverenti <luke.pulverenti@gmail.com> | 2013-03-02 18:27:01 -0500 |
|---|---|---|
| committer | LukePulverenti <luke.pulverenti@gmail.com> | 2013-03-02 18:27:01 -0500 |
| commit | f4f5d31cdec444e3a3fa244581e79251db5e7432 (patch) | |
| tree | 2cd72dfa39bd476524291ec69fdd22c3e16161aa | |
| parent | 72051998e76e772cc22fcd3aa4b4a248b1e5df38 (diff) | |
added nuget readme
| -rw-r--r-- | Nuget/readme.txt | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/Nuget/readme.txt b/Nuget/readme.txt new file mode 100644 index 000000000..3dd1cf65a --- /dev/null +++ b/Nuget/readme.txt @@ -0,0 +1,14 @@ +To update the nuget packages, follow the below procedure: + +1. Build the solution in release mode. This will update the contents of the dll's folder +2. Open each nuspec file, and increment the versions of each, as well as each of the MB dependencies. + +For example, in MediaBrowser.Common.Internal, increment <version>, as well as <dependency id="MediaBrowser.Common" version + +This is quickest using notepad++. It can also be done with nuget package explorer. + +By keeping all the version numbers the same, it makes this largely a mindless activity. If we allow each package to have their own version, this process will be slower and prone to human error. + +3. Once this is done, publish the packages using nuget package explorer. File -> Publish. + +4. Check the nuspec files in right away, otherwise there will be merge conflicts.
\ No newline at end of file |
