The command line version of svn works fine too (but isn't covered here). Visual Studios newer than 2003 can be used, but need some manual tweaks in the project settings. Most versions of Visual Studio Express can be used to build Armstrong and its native plugins, but Buze itself require ATL headers from a non-free version of Visual Studio to build.
Note that you need to add the Python and Python\Scripts directories to your PATH, e.g via Control Panel -> System -> Advanced -> Environment Variables -> System Variables -> PATH.
In most Visual Studios: Go to Tools -> Options -> Projects -> VC++ Directories.
In Visual Studio 2010 Express: Go to the Property Manager and view the properties of "Microsoft.Cpp.Win32.user" under one of the project configurations.
Add paths to executables, includes and libraries. The following paths should be matched in your settings:
Create a new directory, e.g c:\buzesrc, and another empty directory inside it called buze, so you end up with c:\buzesrc\buze.
This way, it is possible to check out the installer sources and documentations in parallell directories later.
Go to c:\buzesrc\buze in Explorer, right-click inside the empty directory and choose "SVN Checkout...".
Enter svn://anders-e.com/buze/trunk/buze as the repository URL. Hit OK and wait for the checkout to complete.
In addition to Boost and the DirectX SDK, there are also several other mandatory libraries required for Armstrong. Pre-built dependency binaries for Windows exist in the win32deps directory in the trunk. This directory must be exported separately and moved into the working copy directory:
Go to c:\buzesrc in Explorer and create a new directory called "deps". Right-click the new directory and choose TortoiseSVN -> Export...Enter svn://anders-e.com/buze/trunk/win32deps as URL for the repository to export. Click OK and wait while TortoiseSVN downloads the dependencies.
When the export is finished, the next step is to move the contents of deps into the buze folder: Go to c:\buzesrc\deps in Explorer and select all the files. Right-click the selected files and choose "Cut". Now go to c:\buzesrc\buze, right-click and select "Paste" to move all files from the deps-directory into the Buze-directory. Answer "Yes to all" to the following question on whether you'd like to overwrite.
In Visual Studio 2005 and newer: The project file conversion automatically enables manifests, but the manifest is already included in the resources. To disable, go to buze -> Properties -> Manifest tool -> Input and output -> Embed Manifest (set to No).
With all the source code and dependencies in place, building should be a matter of opening buze.sln in Visual Studio and choose Build -> Build Solution.