During Windows development it is tricky to switch between 32-bit and 64-bit development modes. To get a raw Qpid checkout started I've developed a script that provides a GUI-like experience (a series of dialog windows . The user specifies the location of the Boost libraries and the in-source or out-of-source build root directories. Then the script runs cmake on the user's behalf to get the build trees started.
From then on the user may double click the qpid-cpp.sln to work in qpid/cpp, or the user may double click a .bat file to launch the .NET binding solution.
Using this scheme a user keeps the QPID_BUILD_ROOT and BOOST_ROOT environment variables set correctly for both DOS box work and for Visual Studio work.