[xbuild] LogExtensions.LogError - disambiguate.

[mono.git] / README.vsnet

diff --git a/README.vsnet b/README.vsnet
index 8d9e421272d5e6b44217e52cb89b2bdf255c6c52..f3a07a1d8c8f7a77b9b8d71a4618538492328963 100644 (file)
--- a/README.vsnet
+++ b/README.vsnet
@@ -1,8 +1,8 @@
-README.vsnet                                   Last updated: 2005-05-26
+README.vsnet                                   Last updated: 2006-02-01
 
 
-SVN now includes a Visual Studio .NET 2005 (beta2) solution, mono.sln,
-and some projects files to build most of the unmanaged parts in Mono.
+SVN includes a Visual Studio .NET 2005 solution, mono.sln, and some 
+projects files to build most of the unmanaged parts in Mono.
 
 The "mono.sln" solution file contains the VC projects files for:
 
@@ -25,17 +25,18 @@ The "mono.sln" solution file contains the VC projects files for:
 
 REQUIREMENTS
 
-* A working cygwin (http://www.cygwin.com/) setup! This is required to:
+* A working (i.e. where you could succesfully build mono) cygwin 
+(http://www.cygwin.com/) setup! This is required to:
        * generate some files (via monoburg and genmdesc);
        * build the class libraries; and
        * test for regressions.
 
-* Visual Studio .NET 2005 beta2. Previous Visual Studio versions may
-work or requires, hopefully minimal, changes.
+* Visual Studio .NET 2005. Previous Visual Studio versions may work or 
+requires, hopefully minimal, changes.
         
-* VSDependencies.zip must be decompressed under /mono/ (otherwise you 
-will need to edit all the projects files. This file can be downloaded 
-from http://www.go-mono.com/archive/VSDependencies.zip
+* VSDependencies.zip must be decompressed under the /mono/ directory 
+(otherwise you will need to edit all the projects files). This file can 
+be downloaded from http://www.go-mono.com/archive/VSDependencies.zip
 
 
 LOCAL CHANGES
@@ -85,9 +86,11 @@ requires a working cygwin environment to create some files (e.g. via
 genmdesc, monoburg). This isn't so bad as without cygwin you wouldn't be
 able to test Mono properly (see REQUIREMENTS);
 
-[3] Only the Debug target is configured properly (easy to fix). Anyway
-there are other issues [1] to fix before switching to Release and IMHO
-the _biggest_ advantage to VS.NET is it's debugger/debugging tools;
+[3] Only the Debug target is configured properly (that would be easy to 
+fix, but would require turning off some optimizations like omitting 
+stack frames). Anyway there are other issues [1] to fix before switching
+to Release and IMHO the _biggest_ advantage to VS.NET is it's debugger/
+debugging tools;
 
 [4] The C compiler emits _lots_ of warning during compilation. Some
 warnings have been turned off for some projects (there was so much that
@@ -101,10 +104,17 @@ Platform SDK (Windows Server 2003 is the latest) to ensure you have the
 latest Windows header files. You can download it from:
 http://www.microsoft.com/msdownload/platformsdk/sdkupdate/psdk-full.htm
 
-[6] Probably a lot more I didn't discover...
+[6] Not everyone has VS.NET so it is possible you may have to add some
+(new) files to the build from time to time. See "more informations" for
+reporting those changes.
 
+[7] Probably a lot more I didn't discover... or has changed since.
 
-MORE INFORMATIONS
+
+MORE INFORMATION
 
 Please email <mono-devel-list@lists.ximian.com> if you have any problem
 and/or if there's something wrong/missing in the instructions.
+
+An online version of this file is available at
+http://www.mono-project.com/Compiling_Mono_VSNET