[mapserver-commits] r13242 -
branches/branch-6-0/docs/en/installation trunk/docs/en/installation
svn at osgeo.org
svn at osgeo.org
Tue Mar 13 17:23:00 EDT 2012
Author: havatv
Date: 2012-03-13 14:22:59 -0700 (Tue, 13 Mar 2012)
New Revision: 13242
Modified:
branches/branch-6-0/docs/en/installation/dotnet.txt
trunk/docs/en/installation/dotnet.txt
Log:
Fixed some too long lines in the generated PDF file - dotnet (#3947).
Modified: branches/branch-6-0/docs/en/installation/dotnet.txt
===================================================================
--- branches/branch-6-0/docs/en/installation/dotnet.txt 2012-03-13 20:08:12 UTC (rev 13241)
+++ branches/branch-6-0/docs/en/installation/dotnet.txt 2012-03-13 21:22:59 UTC (rev 13242)
@@ -34,12 +34,10 @@
Command Prompt and step into the /mapscript/csharp directory. Edit makefile.vc
and set the SWIG variable to the location of your swig.exe
-Use
+Use::
-::
+ nmake -f makefile.vc
- nmake -f makefile.vc
-
to compile mapscript.dll and mapscript_csharp.dll.
@@ -51,11 +49,9 @@
Prompt and step into the /mapscript/csharp directory Edit makefile.vc and set
the SWIG variable to the location of your swig.exe.
-Use
-
-::
+Use::
- nmake -f makefile.vc
+ nmake -f makefile.vc
to compile mapscript.dll and mapscript_csharp.dll.
@@ -64,63 +60,51 @@
Before the compilation you should download and install the recent mono
Win32 setup package (eg. mono-1.1.13.2-gtksharp-2.8.1-win32-1.exe) Edit makefile.vc
and set the CSC variable to the location of your mcs.exe. Alternatively
-you can define
+you can define::
-::
+ MONO = YES
- MONO = YES
-
in your nmake.opt file.
You should use the same compiler for compiling MapScript as the compiler has
been used for the MapServer compilation. To compile MapScript open the Command
-Prompt supplied with your compiler and use
+Prompt supplied with your compiler and use::
-::
+ nmake -f makefile.vc
- nmake -f makefile.vc
-
to compile mapscript.dll and mapscript_csharp.dll.
Alternative compilation methods on Windows
----------------------------------------------
Beginning from MapServer 4.8.3 you can invoke the C# compilation from the
-MapServer directory by uncommenting DOT_NET in nmake.opt
+MapServer directory by uncommenting DOT_NET in nmake.opt::
-::
+ #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ # .NET/C# MapScript
+ # ----------------------------------------------------------------------
+ # .NET will of course only work with MSVC 7.0 and 7.1. Also note that
+ # you will definitely want USE_THREAD defined.
+ #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ #DOT_NET = YES
-#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# .NET/C# MapScript
-# ----------------------------------------------------------------------
-# .NET will of course only work with MSVC 7.0 and 7.1. Also note that
-# you will definitely want USE_THREAD defined.
-#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-#DOT_NET = YES
+and invoking the compilation by::
-and invoking the compilation by
+ nmake -f makefile.vc csharp
-::
+You can also use::
- nmake -f makefile.vc csharp
+ nmake -f makefile.vc install
-You can also use
-
-::
-
- nmake -f makefile.vc install
-
for making the compilation an copying the targets into a common output
directory.
Testing the compilation
---------------------------
-For testing the compilation and the runtime environment you can use
+For testing the compilation and the runtime environment you can use::
-::
+ nmake -f makefile.vc test
- nmake -f makefile.vc test
-
within the csharp directory for starting the sample applications compiled
previously. Before making the test the location of the corresponding libraries
should be included in the system PATH.
@@ -139,20 +123,16 @@
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 at a console step into the /mapscript/csharp directory use.
+compile at a console step into the /mapscript/csharp directory use::
-::
-
- make
+ make
to compile libmapscript.so and mapscript_csharp.dll.
-For testing the compilation and the runtime environment you can use
+For testing the compilation and the runtime environment you can use::
-::
+ make test
- make test
-
for starting the sample applications compiled previously.
OSX compilation targeting the MONO framework
@@ -166,20 +146,16 @@
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
-at a console step into the /mapscript/csharp directory use
+at a console step into the /mapscript/csharp directory use::
-::
-
- make
+ make
to compile libmapscript.dylib and mapscript_csharp.dll.
-For testing the compilation and the runtime environment you can use
+For testing the compilation and the runtime environment you can use::
-::
+ make test
- make test
-
for starting the sample applications compiled previously.
To run the applications mapscript_csharp.dll.config is needed along with the
@@ -199,27 +175,34 @@
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:
+manifest file along with your executable, like::
-::
+ <?xml version="1.0" encoding="utf-8"?>
+ <assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1
+ assembly.adaptive.xsd" manifestVersion="1.0"
+ xmlns:asmv1="urn:schemas-microsoft-com:asm.v1"
+ xmlns:asmv2="urn:schemas-microsoft-com:asm.v2"
+ xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"
+ xmlns="urn:schemas-microsoft-com:asm.v1"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
+ <assemblyIdentity name="drawmap.exe" version="1.0.0.0" type="win32" />
+ <dependency>
+ <dependentAssembly asmv2:dependencyType="install"
+ asmv2:codebase="Microsoft.VC80.CRT.manifest" asmv2:size="522">
+ <assemblyIdentity name="Microsoft.VC80.CRT" version="8.0.50608.0"
+ publicKeyToken="1fc8b3b9a1e18e3b" processorArchitecture="x86"
+ type="win32" />
+ <hash xmlns="urn:schemas-microsoft-com:asm.v2">
+ <dsig:Transforms>
+ <dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
+ </dsig:Transforms>
+ <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
+ <dsig:DigestValue>UMOlhUBGeKRrrg9DaaPNgyhRjyM=</dsig:DigestValue>
+ </hash>
+ </dependentAssembly>
+ </dependency>
+ </assembly>
-<?xml version="1.0" encoding="utf-8"?>
-<assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<assemblyIdentity name="drawmap.exe" version="1.0.0.0" type="win32" />
-<dependency>
-<dependentAssembly asmv2:dependencyType="install" asmv2:codebase="Microsoft.VC80.CRT.manifest" asmv2:size="522">
-<assemblyIdentity name="Microsoft.VC80.CRT" version="8.0.50608.0" publicKeyToken="1fc8b3b9a1e18e3b" processorArchitecture="x86" type="win32" />
-<hash xmlns="urn:schemas-microsoft-com:asm.v2">
-<dsig:Transforms>
-<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
-</dsig:Transforms>
-<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
-<dsig:DigestValue>UMOlhUBGeKRrrg9DaaPNgyhRjyM=</dsig:DigestValue>
-</hash>
-</dependentAssembly>
-</dependency>
-</assembly>
-
This will inform the CLR that your exe depends on the CRT and the proper
assembly wrapper is to be used. If you are using the IDE the manifest file
could be pregenerated by adding a reference to Microsoft.VC80.CRT.manifest
@@ -232,37 +215,37 @@
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:
+dependency. The sample contents of the manifest file are::
-::
+ <?xml version='1.0' encoding='UTF-8' standalone='yes'?>
+ <assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
+ <dependency>
+ <dependentAssembly>
+ <assemblyIdentity type='win32' name='Microsoft.VC80.CRT'
+ version='8.0.50608.0' processorArchitecture='x86'
+ publicKeyToken='1fc8b3b9a1e18e3b' />
+ </dependentAssembly>
+ </dependency>
+ </assembly>
-<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
-<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
-<dependency>
-<dependentAssembly>
-<assemblyIdentity type='win32' name='Microsoft.VC80.CRT' version='8.0.50608.0' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' />
-</dependentAssembly>
-</dependency>
-</assembly>
+Like previously mentioned if you are creating a windows application
+the common language runtime will search for a manifest file for the
+application. The name of the manifest file should be the same as the
+executable append and end with the .manifest extension. However if the
+host process is not controlled by you (like web mapping applications
+using aspnet_wp.exe as the host process) you will not be certain if
+the host process (.exe) will have a manifest containing a reference to
+the CRT wrapper. In this case you may have to embed the manifest into
+the dll as a resource using the mt tool like::
-Like previously mentioned if you are creating a windows application the
-common language runtime will search for a manifest file for the application.
-The name of the manifest file should be the same as the executable append
-and end with the .manifest extension. However if the host process is not
-controlled by you (like web mapping applications using aspnet_wp.exe as
-the host process) you will not be certain if the host process (.exe) will
-have a manifest containing a reference to the CRT wrapper. In this case you
-may have to embed the manifest into the dll as a resource using the mt tool like:
+ mt /manifest mapscript.dll.manifest /outputresource:mapscript.dll;#2
-::
-
- mt /manifest mapscript.dll.manifest /outputresource:mapscript.dll;#2
-
the common language runtime will search for the embedded resource and load
the CRT assembly properly.
-Normally it is enough to load the CRT with the root dll (mapscript.dll),
-but it is not harmful embedding the manifest into the dependent libraries as well.
+Normally it is enough to load the CRT with the root dll
+(mapscript.dll), but it is not harmful embedding the manifest into the
+dependent libraries as well.
Issue with regex and Visual Studio 2005
@@ -279,13 +262,11 @@
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:
+C code (mapscript.dll) takes place using platform invoke like::
-::
+ [DllImport("mapscript", EntryPoint="CSharp_new_mapObj")]
+ public static extern IntPtr new_mapObj(string jarg1);
- [DllImport("mapscript", EntryPoint="CSharp_new_mapObj")]
- public static extern IntPtr new_mapObj(string jarg1);
-
The DllImport declaration contains the library name, however to transform
the library name into a file name is platform dependent. On Windows the library
name is simply appended with the .dll extension (mapscript.dll). On the Unix
@@ -295,21 +276,17 @@
Mapping of the library name may be manually controlled using a dll.config
file. This simply maps the library file the DllImport is looking for to its
unix equivalent. The file normally contains the following information
-(mapscript_csharp.dll.config):
+(mapscript_csharp.dll.config)::
-::
+ <configuration>
+ <dllmap dll="mapscript" target="libmapscript.so" />
+ </configuration>
-<configuration>
-<dllmap dll="mapscript" target="libmapscript.so" />
-</configuration>
+and with the OSX builds::
-and with the OSX builds:
-
-::
-
-<configuration>
-<dllmap dll="mapscript" target="libmapscript.dylib" />
-</configuration>
+ <configuration>
+ <dllmap dll="mapscript" target="libmapscript.dylib" />
+ </configuration>
The file should be placed along with the corresponding mapscript_csharp.dll
file, and created by default during the make process. For more information see:
@@ -325,12 +302,10 @@
decimal separator is other than "." inside the locale of the process may cause
parse errors when the mapfile contains float numbers. Since the MONO process
takes over the locale settings of the environment it is worth considering to
-set the default locale to "C" of the host process, like:
+set the default locale to "C" of the host process, like::
-::
+ LC_ALL=C mono ./drawmap.exe ../../tests/test.map test_csharp.png
- LC_ALL=C mono ./drawmap.exe ../../tests/test.map test_csharp.png
-
Most frequent errors
=======================
@@ -340,16 +315,18 @@
Unable to load dll (MapScript)
----------------------------------
-You can get this problem on Windows and in most cases it can be dedicated to a
-missing or an unloadable shared library. The error message talks about
-mapscript.dll but surely one or more of the dll-s are missing that libmap.dll
-depends on. So firstly you might want to check for the dependencies of your
-libmap.dll in your application directory. You can use the Visual Studio
-Dependency Walker to accomplish this task. You can also use a file monitoring
-tool (like SysInternal's filemon) to detect the dll-s that could not be loaded.
-I propose to store all of the dll-s required by your application in the
-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 can get this problem on Windows and in most cases it can be
+dedicated to a missing or an unloadable shared library. The error
+message talks about mapscript.dll but surely one or more of the dll-s
+are missing that libmap.dll depends on. So firstly you might want to
+check for the dependencies of your libmap.dll in your application
+directory. You can use the Visual Studio Dependency Walker to
+accomplish this task. You can also use a file monitoring tool (like
+SysInternal's filemon) to detect the dll-s that could not be loaded.
+I propose to store all of the dll-s required by your application in
+the 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
desktop and the ASP.NET applications. Although you can run the drawmap sample
Modified: trunk/docs/en/installation/dotnet.txt
===================================================================
--- trunk/docs/en/installation/dotnet.txt 2012-03-13 20:08:12 UTC (rev 13241)
+++ trunk/docs/en/installation/dotnet.txt 2012-03-13 21:22:59 UTC (rev 13242)
@@ -34,12 +34,10 @@
Command Prompt and step into the /mapscript/csharp directory. Edit makefile.vc
and set the SWIG variable to the location of your swig.exe
-Use
+Use::
-::
+ nmake -f makefile.vc
- nmake -f makefile.vc
-
to compile mapscript.dll and mapscript_csharp.dll.
@@ -51,11 +49,9 @@
Prompt and step into the /mapscript/csharp directory Edit makefile.vc and set
the SWIG variable to the location of your swig.exe.
-Use
-
-::
+Use::
- nmake -f makefile.vc
+ nmake -f makefile.vc
to compile mapscript.dll and mapscript_csharp.dll.
@@ -64,63 +60,51 @@
Before the compilation you should download and install the recent mono
Win32 setup package (eg. mono-1.1.13.2-gtksharp-2.8.1-win32-1.exe) Edit makefile.vc
and set the CSC variable to the location of your mcs.exe. Alternatively
-you can define
+you can define::
-::
+ MONO = YES
- MONO = YES
-
in your nmake.opt file.
You should use the same compiler for compiling MapScript as the compiler has
been used for the MapServer compilation. To compile MapScript open the Command
-Prompt supplied with your compiler and use
+Prompt supplied with your compiler and use::
-::
+ nmake -f makefile.vc
- nmake -f makefile.vc
-
to compile mapscript.dll and mapscript_csharp.dll.
Alternative compilation methods on Windows
----------------------------------------------
Beginning from MapServer 4.8.3 you can invoke the C# compilation from the
-MapServer directory by uncommenting DOT_NET in nmake.opt
+MapServer directory by uncommenting DOT_NET in nmake.opt::
-::
+ #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ # .NET/C# MapScript
+ # ----------------------------------------------------------------------
+ # .NET will of course only work with MSVC 7.0 and 7.1. Also note that
+ # you will definitely want USE_THREAD defined.
+ #~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ #DOT_NET = YES
-#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-# .NET/C# MapScript
-# ----------------------------------------------------------------------
-# .NET will of course only work with MSVC 7.0 and 7.1. Also note that
-# you will definitely want USE_THREAD defined.
-#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-#DOT_NET = YES
+and invoking the compilation by::
-and invoking the compilation by
+ nmake -f makefile.vc csharp
-::
+You can also use::
- nmake -f makefile.vc csharp
+ nmake -f makefile.vc install
-You can also use
-
-::
-
- nmake -f makefile.vc install
-
for making the compilation an copying the targets into a common output
directory.
Testing the compilation
---------------------------
-For testing the compilation and the runtime environment you can use
+For testing the compilation and the runtime environment you can use::
-::
+ nmake -f makefile.vc test
- nmake -f makefile.vc test
-
within the csharp directory for starting the sample applications compiled
previously. Before making the test the location of the corresponding libraries
should be included in the system PATH.
@@ -139,20 +123,16 @@
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 at a console step into the /mapscript/csharp directory use.
+compile at a console step into the /mapscript/csharp directory use::
-::
-
- make
+ make
to compile libmapscript.so and mapscript_csharp.dll.
-For testing the compilation and the runtime environment you can use
+For testing the compilation and the runtime environment you can use::
-::
+ make test
- make test
-
for starting the sample applications compiled previously.
OSX compilation targeting the MONO framework
@@ -166,20 +146,16 @@
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
-at a console step into the /mapscript/csharp directory use
+at a console step into the /mapscript/csharp directory use::
-::
-
- make
+ make
to compile libmapscript.dylib and mapscript_csharp.dll.
-For testing the compilation and the runtime environment you can use
+For testing the compilation and the runtime environment you can use::
-::
+ make test
- make test
-
for starting the sample applications compiled previously.
To run the applications mapscript_csharp.dll.config is needed along with the
@@ -199,27 +175,34 @@
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:
+manifest file along with your executable, like::
-::
+ <?xml version="1.0" encoding="utf-8"?>
+ <assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1
+ assembly.adaptive.xsd" manifestVersion="1.0"
+ xmlns:asmv1="urn:schemas-microsoft-com:asm.v1"
+ xmlns:asmv2="urn:schemas-microsoft-com:asm.v2"
+ xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"
+ xmlns="urn:schemas-microsoft-com:asm.v1"
+ xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
+ <assemblyIdentity name="drawmap.exe" version="1.0.0.0" type="win32" />
+ <dependency>
+ <dependentAssembly asmv2:dependencyType="install"
+ asmv2:codebase="Microsoft.VC80.CRT.manifest" asmv2:size="522">
+ <assemblyIdentity name="Microsoft.VC80.CRT" version="8.0.50608.0"
+ publicKeyToken="1fc8b3b9a1e18e3b" processorArchitecture="x86"
+ type="win32" />
+ <hash xmlns="urn:schemas-microsoft-com:asm.v2">
+ <dsig:Transforms>
+ <dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
+ </dsig:Transforms>
+ <dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
+ <dsig:DigestValue>UMOlhUBGeKRrrg9DaaPNgyhRjyM=</dsig:DigestValue>
+ </hash>
+ </dependentAssembly>
+ </dependency>
+ </assembly>
-<?xml version="1.0" encoding="utf-8"?>
-<assembly xsi:schemaLocation="urn:schemas-microsoft-com:asm.v1 assembly.adaptive.xsd" manifestVersion="1.0" xmlns:asmv1="urn:schemas-microsoft-com:asm.v1" xmlns:asmv2="urn:schemas-microsoft-com:asm.v2" xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" xmlns="urn:schemas-microsoft-com:asm.v1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
-<assemblyIdentity name="drawmap.exe" version="1.0.0.0" type="win32" />
-<dependency>
-<dependentAssembly asmv2:dependencyType="install" asmv2:codebase="Microsoft.VC80.CRT.manifest" asmv2:size="522">
-<assemblyIdentity name="Microsoft.VC80.CRT" version="8.0.50608.0" publicKeyToken="1fc8b3b9a1e18e3b" processorArchitecture="x86" type="win32" />
-<hash xmlns="urn:schemas-microsoft-com:asm.v2">
-<dsig:Transforms>
-<dsig:Transform Algorithm="urn:schemas-microsoft-com:HashTransforms.Identity" />
-</dsig:Transforms>
-<dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
-<dsig:DigestValue>UMOlhUBGeKRrrg9DaaPNgyhRjyM=</dsig:DigestValue>
-</hash>
-</dependentAssembly>
-</dependency>
-</assembly>
-
This will inform the CLR that your exe depends on the CRT and the proper
assembly wrapper is to be used. If you are using the IDE the manifest file
could be pregenerated by adding a reference to Microsoft.VC80.CRT.manifest
@@ -232,37 +215,37 @@
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:
+dependency. The sample contents of the manifest file are::
-::
+ <?xml version='1.0' encoding='UTF-8' standalone='yes'?>
+ <assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
+ <dependency>
+ <dependentAssembly>
+ <assemblyIdentity type='win32' name='Microsoft.VC80.CRT'
+ version='8.0.50608.0' processorArchitecture='x86'
+ publicKeyToken='1fc8b3b9a1e18e3b' />
+ </dependentAssembly>
+ </dependency>
+ </assembly>
-<?xml version='1.0' encoding='UTF-8' standalone='yes'?>
-<assembly xmlns='urn:schemas-microsoft-com:asm.v1' manifestVersion='1.0'>
-<dependency>
-<dependentAssembly>
-<assemblyIdentity type='win32' name='Microsoft.VC80.CRT' version='8.0.50608.0' processorArchitecture='x86' publicKeyToken='1fc8b3b9a1e18e3b' />
-</dependentAssembly>
-</dependency>
-</assembly>
+Like previously mentioned if you are creating a windows application
+the common language runtime will search for a manifest file for the
+application. The name of the manifest file should be the same as the
+executable append and end with the .manifest extension. However if the
+host process is not controlled by you (like web mapping applications
+using aspnet_wp.exe as the host process) you will not be certain if
+the host process (.exe) will have a manifest containing a reference to
+the CRT wrapper. In this case you may have to embed the manifest into
+the dll as a resource using the mt tool like::
-Like previously mentioned if you are creating a windows application the
-common language runtime will search for a manifest file for the application.
-The name of the manifest file should be the same as the executable append
-and end with the .manifest extension. However if the host process is not
-controlled by you (like web mapping applications using aspnet_wp.exe as
-the host process) you will not be certain if the host process (.exe) will
-have a manifest containing a reference to the CRT wrapper. In this case you
-may have to embed the manifest into the dll as a resource using the mt tool like:
+ mt /manifest mapscript.dll.manifest /outputresource:mapscript.dll;#2
-::
-
- mt /manifest mapscript.dll.manifest /outputresource:mapscript.dll;#2
-
the common language runtime will search for the embedded resource and load
the CRT assembly properly.
-Normally it is enough to load the CRT with the root dll (mapscript.dll),
-but it is not harmful embedding the manifest into the dependent libraries as well.
+Normally it is enough to load the CRT with the root dll
+(mapscript.dll), but it is not harmful embedding the manifest into the
+dependent libraries as well.
Issue with regex and Visual Studio 2005
@@ -279,13 +262,11 @@
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:
+C code (mapscript.dll) takes place using platform invoke like::
-::
+ [DllImport("mapscript", EntryPoint="CSharp_new_mapObj")]
+ public static extern IntPtr new_mapObj(string jarg1);
- [DllImport("mapscript", EntryPoint="CSharp_new_mapObj")]
- public static extern IntPtr new_mapObj(string jarg1);
-
The DllImport declaration contains the library name, however to transform
the library name into a file name is platform dependent. On Windows the library
name is simply appended with the .dll extension (mapscript.dll). On the Unix
@@ -295,21 +276,17 @@
Mapping of the library name may be manually controlled using a dll.config
file. This simply maps the library file the DllImport is looking for to its
unix equivalent. The file normally contains the following information
-(mapscript_csharp.dll.config):
+(mapscript_csharp.dll.config)::
-::
+ <configuration>
+ <dllmap dll="mapscript" target="libmapscript.so" />
+ </configuration>
-<configuration>
-<dllmap dll="mapscript" target="libmapscript.so" />
-</configuration>
+and with the OSX builds::
-and with the OSX builds:
-
-::
-
-<configuration>
-<dllmap dll="mapscript" target="libmapscript.dylib" />
-</configuration>
+ <configuration>
+ <dllmap dll="mapscript" target="libmapscript.dylib" />
+ </configuration>
The file should be placed along with the corresponding mapscript_csharp.dll
file, and created by default during the make process. For more information see:
@@ -325,12 +302,10 @@
decimal separator is other than "." inside the locale of the process may cause
parse errors when the mapfile contains float numbers. Since the MONO process
takes over the locale settings of the environment it is worth considering to
-set the default locale to "C" of the host process, like:
+set the default locale to "C" of the host process, like::
-::
+ LC_ALL=C mono ./drawmap.exe ../../tests/test.map test_csharp.png
- LC_ALL=C mono ./drawmap.exe ../../tests/test.map test_csharp.png
-
Most frequent errors
=======================
@@ -340,16 +315,18 @@
Unable to load dll (MapScript)
----------------------------------
-You can get this problem on Windows and in most cases it can be dedicated to a
-missing or an unloadable shared library. The error message talks about
-mapscript.dll but surely one or more of the dll-s are missing that libmap.dll
-depends on. So firstly you might want to check for the dependencies of your
-libmap.dll in your application directory. You can use the Visual Studio
-Dependency Walker to accomplish this task. You can also use a file monitoring
-tool (like SysInternal's filemon) to detect the dll-s that could not be loaded.
-I propose to store all of the dll-s required by your application in the
-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 can get this problem on Windows and in most cases it can be
+dedicated to a missing or an unloadable shared library. The error
+message talks about mapscript.dll but surely one or more of the dll-s
+are missing that libmap.dll depends on. So firstly you might want to
+check for the dependencies of your libmap.dll in your application
+directory. You can use the Visual Studio Dependency Walker to
+accomplish this task. You can also use a file monitoring tool (like
+SysInternal's filemon) to detect the dll-s that could not be loaded.
+I propose to store all of the dll-s required by your application in
+the 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
desktop and the ASP.NET applications. Although you can run the drawmap sample
More information about the mapserver-commits
mailing list