[mapserver-commits] r8383 - trunk/docs/installation
svn at osgeo.org
svn at osgeo.org
Sat Jan 3 11:19:20 EST 2009
Author: jmckenna
Date: 2009-01-03 11:19:20 -0500 (Sat, 03 Jan 2009)
New Revision: 8383
Modified:
trunk/docs/installation/dotnet.txt
Log:
common header, correct references to 'MapServer' and 'MapScript', add library version warning
Modified: trunk/docs/installation/dotnet.txt
===================================================================
--- trunk/docs/installation/dotnet.txt 2009-01-03 15:38:44 UTC (rev 8382)
+++ trunk/docs/installation/dotnet.txt 2009-01-03 16:19:20 UTC (rev 8383)
@@ -8,22 +8,24 @@
:Contact: szekerest at gmail.com
:Revision: $Revision$
:Date: $Date$
-:Last Updated: 2006/10/11
Compilation
==============
-Before compiling C# mapscript you should compile mapserver with the options
+Before compiling C# mapscript you should compile MapServer with the options
for your requirements. For more information about the compilation of
-MapServer please see :ref:`Win32 Compilation and Installation <win32>`. It is highly
-recommended to minimize the library dependency of your application, so when
-compiling mapserver enable only the features really needed. To compile the
-C# binding SWIG 1.3.31 or later is required.
+MapServer please see :ref:`Win32 Compilation and Installation Guide <win32>`.
+It is highly recommended to minimize the library dependency of your application,
+so when compiling MapServer enable only the features really needed. To
+compile the C# binding SWIG 1.3.31 or later is required.
+.. warning::
+ This document may refer to older library versions. You may want to try
+ to use more recent library versions for your build.
Win32 compilation targeting the MS.NET framework 1.1
--------------------------------------------------------
-You should compile mapserver, mapscript and all of the subsequent libraries
+You should compile MapServer, mapscript and all of the subsequent libraries
using Visual Studio 2003. Download and uncompress the latest SWIGWIN package
that contains the precompiled swig.exe Open the Visual Studio .NET 2003
Command Prompt and step into the /mapscript/csharp directory. Edit makefile.vc
@@ -40,7 +42,7 @@
Win32 compilation targeting the MS.NET framework 2.0
--------------------------------------------------------
-You should compile mapserver, mapscript and all of the subsequent libraries
+You should compile MapServer, MapScript and all of the subsequent libraries
using Visual Studio 2005. Download and uncompress the latest SWIGWIN package
that contains the precompiled swig.exe Open the Visual Studio 2005 Command
Prompt and step into the /mapscript/csharp directory Edit makefile.vc and set
@@ -79,7 +81,7 @@
Alternative compilation methods on Windows
----------------------------------------------
-Beginning from mapserver 4.8.3 you can invoke the C# compilation from the
+Beginning from MapServer 4.8.3 you can invoke the C# compilation from the
MapServer directory by uncommenting DOT_NET in nmake.opt
::
@@ -129,7 +131,7 @@
probably compile it from the source if pre-compiled binaries are not available
for your platform.
-Before compiling mapscript mapserver should be configured and compiled.
+Before compiling MapScript, MapServer should be configured and compiled.
Beginning from MapServer 4.8.2 during configuration the
mapscript/csharp/Makefile will be created according to the configuration
options. Edit this file and set the SWIG and CSC for the corresponding
@@ -156,8 +158,8 @@
Beginning from 4.10.0 the csharp/Makefile supports the OSX builds. Before
making the build the recent MONO package should be installed on the system.
-Before compiling mapscript mapserver should be configured and compiled.
-Beginning from mapserver 4.8.2 during configuration the
+Before compiling MapScript, MapServer should be configured and compiled.
+Beginning from MapServer 4.8.2 during configuration the
mapscript/csharp/Makefile will be created according to the configuration
options. Edit this file and set the SWIG and CSC for the corresponding
executable pathes if the files could not be accessed by default. To compile
@@ -192,7 +194,7 @@
Visual Studio 2005 requires a manifest file to load the CRT native assembly wrapper
---------------------------------------------------------------------------------------
-If you have compiled mapserver for using the CRT libraries and you are using
+If you have compiled MapServer for using the CRT libraries and you are using
the MS.NET framework 2.0 as the execution runtime you should supply a proper
manifest file along with your executable, like:
@@ -224,7 +226,7 @@
Manifests for the dll-s must be embedded as a resource
----------------------------------------------------------
-According to the windows makefile the mapscript compilation target
+According to the windows makefile the MapScript compilation target
(mapscript.dll) is linked with the /MD option. In this case the VS2005
linker will generate a manifest file containing the unmanaged assembly
dependency. The sample contents of the manifest file are:
@@ -269,10 +271,10 @@
http://trac.osgeo.org/mapserver/ticket/1651
-C# mapscript library name mapping with MONO
------------------------------------------------
+C# MapScript library name mapping with MONO
+-------------------------------------------
-Using the mapscript interface created by the SWIG interface generator the
+Using the MapScript interface created by the SWIG interface generator the
communication between the C# wrapper classes (mapscript_csharp.dll) and the
C code (mapscript.dll) takes place using platform invoke like:
@@ -332,7 +334,7 @@
This chapter will summarize the most frequent problems the user can run into.
The issues were collected mainly from the -users list and the IRC.
-Unable to load dll (mapscript)
+Unable to load dll (MapScript)
----------------------------------
You can get this problem on Windows and in most cases it can be dedicated to a
@@ -346,7 +348,7 @@
application folder. If you can run the drawmap C# sample application with
your mapfile your compilation might be correct and all of the dlls are available.
-You may find that the mapscript C# interface behaves differently for the
+You may find that the MapScript C# interface behaves differently for the
desktop and the ASP.NET applications. Although you can run the drawmap sample
correctly you may encounter the dll loading problem with the ASP.NET
applications. When creating an ASP.NET project your application folder will
@@ -361,6 +363,6 @@
Bug reports
==============
-If you find a problem dedicated to the mapscript C# interface feel free to
-file a bug report to Trac.
+If you find a problem dedicated to the MapScript C# interface feel free to
+file a bug report to the `Issue Tracker <http://trac.osgeo.org/mapserver>`__.
More information about the mapserver-commits
mailing list