Binaries
We produce binaries of our source-tree and compiled assemblies every time anyone commits. These are recommended if you're unable to use Git or Subversion
Git and Subversion repository information and downloads list is available on the main downloads page, and will be updated whenever new releases are available.
First things first, you need to get the source code. Until releases are available, the best way to do this is to do a checkout from source-control; we recommend this because the source-code isn't in a stable state yet, so it's a good idea to update your copy regularly and this is easiest done if you have a working copy. Depending on your client, the method of performing a checkout may differ.
Our primary source-control is Git using Github, but we also provide a Subversion mirror for those of you that haven't made the switch. We recommend you use Git whenever possible.
If you're using git, you have two options available to you. If you plan on modifying Fluent NHibernate and contributing back to us, then you're best forking our repository and sending us a pull request. You can find out more about that on the github guides site: forking and pull requests. The other option is a direct clone off our repository, but that will leave you in an awkward state if you ever do plan to contribute (but it's fine if you don't).
Our repository is located at: http://github.com/jagregory/fluent-nhibernate
Again, we recommend forking our repository; if you don't want to do that, you can do a direct clone:
git clone git://github.com/jagregory/fluent-nhibernate.git
Subversion access still remains via a read-only mirror.
svn co http://fluent-nhibernate.googlecode.com/svn/trunk/ fluent-nhibernate
Tortoise SVN
Right click in a folder and choose SVN Checkout..., from the dialog that appears enter http://fluent-nhibernate.googlecode.com/svn/trunk/ as the URL of repository, then set your checkout location and click OK.
Once you've got a copy on your local machine, there are two ways you can do a build.
InstallGems.bat from the Fluent NHibernate root directory; this makes sure your machine has all the gems required to build successfully. Once that's completed, and for all subsequent builds, you need to run Build.bat; this batch file runs our Rake script which builds the standard NHibernate 2.0 version and outputs it in the build directory. For more options for building, see the details of our Rake Script.src\FluentNHibernate.sln solution in Visual Studio and do a build, you can optionally run the tests too.Now that you've got Fluent NHibernate built, you just need to reference the FluentNHibernate.dll assembly in your project.
What next? Your first project