<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
I belive you need all dll files in the "bin" folder.<br>
I choose another name for my managed API dll, so you may take all the
dll's <br>
from an installation and copy them into the bin/app folder of the
executeable.<br>
<br>
I would very much like a layer like the one used in MapStudio to be a
part of the MapGuide API.<br>
Unfortunately there are three languages that has to be supported.<br>
So, unless someone writes and maintains an equivalent API for PHP and
JSP, it can only be included as an add-on.<br>
<br>
The main benefits of using the managed http layer, is that it can be
made independant of the server version, and communicates on port 80.<br>
This means that the program that is using the server, does not need to
have any special port or setup, unlike the standard API.<br>
The drawback, is that http is a bit slow, compared to direct
communication with the server.<br>
<pre class="moz-signature" cols="72">Regards, Kenneth, GEOGRAF A/S
</pre>
<br>
<br>
Maksim Sestic skrev:
<blockquote cite="mid:15517230.post@talk.nabble.com" type="cite">
<pre wrap="">Kenneth, thanks a lot for the clarification. Do you, by any chance, keep a
list of unmanaged libraries used by MapGuideNativeAPI.dll in case it uses
native MGOS connection object to connect to the server (DllImport-ed ones)?
I'm just trying to keep the list short as much as possible :-)
If certain MG-based FDO operations are not currently supported on
HttpServerConnection level, I guess I'll have to get around MG and talk to
managed FDO libraries directly, but this is a lesser problem.
IMHO, MG community is currently aware of MapStudio OS as a counterpart of
MapGuide Studio, but this managed layer underneath (MapGuideAPI.dll) is even
more interesting. Both MGOS and MGE do lack usable managed layer, I hope
someone (you?) will introduce a motion/RFC to adopt it as a standard
supplement to both.
Regards,
Maksim Sestic
Kenneth, GEOGRAF A/S wrote:
</pre>
<blockquote type="cite">
<pre wrap="">The code for the MapGuideNativeAPI.dll is present in the sourcecode for
MapStudioOS (look in MapGuideAPI/NativeAPIWrapper).
This code is generated with the MapGuide Open Source SWiG build, but I
removed all .Net 2.0 stuff, and replaced it with .Net 1.1 counterparts.
Recently I have modified the generated code a bit, so that it will run
on both 1.2 MapGuide dll's and 2.0 dll's.
The MapGuideNativeAPI.dll is almost the same as the one distributed as
MapGuideDotNetApi.dll (with the diffs mentioned above).
If you wish to use some of the more "advanced" stuff, where you can
modify classes instead of Xml, you have to reference the MapGuideAPI.dll.
This DLL offers two connections to the MapGuide Server, namely
HttpServerConnection and LocalNativeConnection.
The first one is 100% managed and does not use/need the Binaries shipped
with MapGuide.
The second one uses the MapGuideNativeAPI.dll to access the MapGuide
binaries (dll files), and connects with those.
Both types of connection offers an identical set of methods to
read/write MapGuide data as classes, rather than Xml.
Unfortunately the Http interface does not support all the features of
the NativeAPI, so some features are only accessible
by calling that directly (missing methods are mainly related to FDO
create/update).
You can mix and match as you like, I see no problems in using both API
models at the same time.
I have tested the code with both MGOS and MGE, I even have special code
to handle MGE 2007 runtime maps :).
FYI, the HttpServerConnection is more extensively tested than the
LocalNativeConnection.
Regards, Kenneth, GEOGRAF A/S
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
</body>
</html>