On workaround would be to open the correct port in the firewall, but
that will probably open up all sorts of security hazards.
Another solution is to create a .Net wrapper for the HTTP interface of
the mapguide server.
I have built such a wrapper, and licensed it under LGPL.
It is not complete
You can utilise the .net API in a windows client application only if the host
which the client application will run, can reach the mapguide site server,
because the mapguide API is meant to be used on a server/web "tier".
If this is not what you are after, then unfortunately you cannot use the
.n
