[fdo-internals] Provider registry...

[Robert Fortin]

We used to do that through a custom action using the API as part of the merge module/msi.
But regfdo makes plenty of sense since the info on the provider that gets included in the providers.xml is all be available through the dll.
That way you can add a new/remove dll and un/register it easily.
Good idea.

RF

-----Original Message-----
From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Monday, April 21, 2008 7:09 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] Provider registry...

I hadn't considered the option (honestly, didn't know the API existed).

I think that would be useful if the provider was packaged in some kind
of installer (MSI, NSIS, whatever) where you could run a loader app, but
for a simple distribution (just a bunch of files) I don't see how I
could leverage this API.

Maybe FDO could distribute a utility like regsvr32 but for FDO
providers? :)  That way, the user could just copy the DLL(s) into the
FDO bin directory, and run "regfdo myprovider.dll" on the provider DLL
and it would automatically add itself...

Jason

-----Original Message-----
From: Robert Fortin
Subject: RE: [fdo-internals] Provider registry...

FDO has a mechanism to register/deregister a provider.  This actually
add/remove the entries in the providers.xml by calling an API.  This can
be done as part of the installation of the provider. That's what we have
been doing in the past where each provider was registering itself.  If
for some reason the registery mechanism changes (which actually happened
in the past) it is hidden by the API.  Have you consider this option?
_______________________________________________
fdo-internals mailing list
fdo-internals at lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/fdo-internals