commitmonitor Code

--- a/trunk/build.txt
+++ b/trunk/build.txt
@@ -1,17 +1,10 @@
 First, you need to install the compiler package.
 
-- You need VS.NET2008 (or at least Visual C++ .NET 2008) 
+- You need VS.NET2008
   If you want to build the msi make sure the "Tools for Redistributing
   Applications" are installed.
   Also, you need the MFC feature pack which contains the tr1 c-runtime
   extensions.
-
-- If you do not have access to VS.NET you can download the free
-  Visual C++ 2008 Express Edition.
-  - Install Visual C++ 200 Express Edition.
-    Download it from http://msdn.microsoft.com/vstudio/express/visualc/
-  - Install Microsoft SDK for Windows Vista (February 2007 Update)
-      - http://www.microsoft.com/downloads/details.aspx?FamilyID=FF6467E6-5BBA-4BF5-B562-9199BE864D29
 
 Next you need to install some utilities/programs:
 - Python 2.4(*)           : http://www.python.org/windows/
@@ -34,25 +27,8 @@
 Building packages
 
   Hint: before you can start building CommitMonitor, you need to call the vsvars32.bat
-  file which is located in %VS80COMNTOOLS%. 
+  file which is located in %VS90COMNTOOLS%. 
   
-  Note that for the Express edition you need to sort out the vars for the platform SDK
-  as well. The easiest way I found was to edit the supplied VC++ file
-  C:\Program Files\Microsoft Visual Studio 8\VC\vcvarsall.bat
-  Look for the :x86 label and add an extra call to setenv.cmd as shown below:
-
-	:x86
-	if not exist "%~dp0bin\vcvars32.bat" goto missing
-	call "%~dp0bin\vcvars32.bat"
-	if exist "%ProgramFiles%\Microsoft SDKs\Windows\v6.0\bin\setenv.cmd" call "%ProgramFiles%\Microsoft SDKs\Windows\v6.0\bin\setenv.cmd" /Release /x86 /vista
-	if exist "%ProgramFiles%\Microsoft SDKs\Windows\v6.0\bin\setenv.cmd" goto :eof
-	if exist "%ProgramFiles%\Microsoft Platform SDK\setenv.cmd" call "%ProgramFiles%\Microsoft Platform SDK\setenv.cmd"
-	if exist "%ProgramFiles%\Microsoft Platform SDK\setenv.cmd" goto :eof
-	goto :eof
-
-  Then call vsvarsall.bat when you start your command processor instead
-  of vsvars32 as described above.
-
   > nant
   will show you some help about the targets you can use
 
@@ -73,18 +49,5 @@
   which will create a build log file which you can use to analyse where
   exactly the build failed.
 
-  If you are building using VC++ Express, your options are somewhat limited.
-  Firstly you need to change the build tool in default.build.user.
-  There is already a line to set this up which you need to un-comment:
-
-	<property name="buildtool" value="vcexpress.exe" />
-
-  Note that the VC Express compiler works in the background without a console
-  window. There is a lot of disk activity with no apparent result showing
-  in the Nant console window. Be patient!
-
-  Before building the applications, update the version info:
-  > nant VersionInfo
-
 
   After the script finished, the packages can be found in .\bin .

--- a/trunk/default.build.user.tmpl
+++ b/trunk/default.build.user.tmpl
@@ -14,16 +14,10 @@
 
 <project name="ToolPaths" default="env">
 
-<!-- ====================================================================== -->
-<!-- These two targets have to exist in doc.build.user                      -->
-<!-- ====================================================================== -->
-
-	<target name="VSNET" description="Checks if the env variables for VS.NET2005 are set">
+	<target name="VSNET" description="Checks if the env variables for VS.NET2008 are set">
 		<if test="${not environment::variable-exists('VCINSTALLDIR')}">
 			<fail>You must first call "%VS90COMNTOOLS%\vsvars32.bat"</fail>
 		</if>
-		<!-- Uncomment the line below to allow limited building using VC Express instead of VS.NET. -->
-		<!-- <property name="buildtool" value="vcexpress.exe" /> -->
 	</target>
 
 	<target name="env">