- Open
ReactiveUI.sln
in VS2012 / VS2013 - Run tests, build ReactiveUI.sln in VS2012 on Win8
- Submit PR
- Fork and Clone the source
- Create a new branch for your feature / bugfix
- Open the ReactiveUI.sln solution - this is the one you should use unless you're hacking on platform-specific code.
- Run all the tests, make sure they pass.
- Write some new tests that fail
- Make your change
- See those same tests pass! Hurrah!
- Push that branch to GitHub (
git push -u origin my-cool-new-feature
) - Go to your fork on GitHub, you should see a button with your branch next to it labeled 'Pull Request'
- Type up some information about your change
This looks hard, but once you get your environment set up, it's really only 'Build in VS, build in Mono, run script'
- Put the source into DropBox or another way you can share the same folder between a Mac and a PC (Parallels Shared Folders works too)
- Edit
/CommonAssemblyInfo.cs
and bump the version - Open ReactiveUI.sln and build it in Release mode under VS2012 on Windows 8 / Win8.1 with the WP8 SDK installed (nothing earlier is supported)
- Open MonoDevelop, and build ReactiveUI_XSAll.sln in Release mode
- Back on the PC, run
MakeRelease.ps1
and specify a NuGet SemVer, likeMakeRelease.ps1 -version "5.5.0-beta1"
- You'll end up with two new folders,
Release
andNuget-Release
, as well as the.nupkg
files in the root directory.
- The only 100% guaranteed .sln files to be maintained are ReactiveUI.sln and ReactiveUI_XSAll.sln - the others may be missing projects
- Please follow my coding convention when submitting PRs -
if
statements have the brackets on the same line, non-public methods shouldBeCasedLikeThis, etc etc. I know I'm weird, Deal With It(tm).