[fdo-internals] Problems createing a Managed FDO Provider using C#
badreddine.karoui at autodesk.com
Mon Nov 19 11:54:34 EST 2007
There is no support for managed providers in Fdo. Many Fdo consumers, like MapGuide Open source, are already using the unmanaged Fdo API and you will require an unmanaged bridge if you want your provider to be used by those clients.
This bridge can be an other Fdo common component which can provide support for managed providers. May be your mixed solution can be refactored into a common unmanaged/managed Fdo bridge and a managed provider.
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of geostarter
Sent: Monday, November 19, 2007 11:37 AM
To: fdo-internals at lists.osgeo.org
Subject: [fdo-internals] Problems createing a Managed FDO Provider using C#
I'm interested to write a managed FDO Provider using C#. I have already
implemented a part of the provider and i have tried to use it with the
ConnectionManager of the FDO API.
I also have changed the type of the provider in the providers.xml to
IsManaged=true. But the ConnectionManager ist not able to load the manged
assembly. I always get the error "entry point CreateConnection not found".
It seems that the ConnectionManager always will load an unmanaged assembly.
I have tried to us a mixed mode assembly and this works very fine, but i
would prefer to use a "complete manged provider" implementation.
Is a managed provider not working until now or is there a mistake in my
Thanks for your help
View this message in context: http://www.nabble.com/Problems-createing-a-Managed-FDO-Provider-using-C--tf4836687s18162.html#a13837039
Sent from the fdo-internals mailing list archive at Nabble.com.
fdo-internals mailing list
fdo-internals at lists.osgeo.org
More information about the fdo-internals