AW: [fdo-users] FDO 3.4 final broke my toolbox

[Aaron Pieler]

A little hint would be: DELAYLOAD
I'm currently not sure if this was introduced between RC1 and Final. You
have to look at the subversion log.
But I had the same problem a few weeks ago.
I added the path where the binaries are to the environment-variable PATH.
For example in .NET:
            string varPath =
System.Environment.GetEnvironmentVariable("PATH");
            varPath = String.Concat(varPath, ";", fdoBinariesLocation);
            System.Environment.SetEnvironmentVariable("PATH",
varPath,EnvironmentVariableTarget.Process);



-----Ursprüngliche Nachricht-----
Von: fdo-users-bounces at lists.osgeo.org
[mailto:fdo-users-bounces at lists.osgeo.org] Im Auftrag von Jackie Ng
Gesendet: Freitag, 17. April 2009 09:29
An: fdo-users at lists.osgeo.org
Betreff: Re: [fdo-users] FDO 3.4 final broke my toolbox



Okay, the exceptions occur when I have the FDO binaries in a folder that
doesn't have the FDO Toolbox binaries (default is the "FDO" subdirectory of
the FDO Toolbox directory). If I move the binaries into the main directory
(with the FDO Toolbox binaries) things work.

So the real problem is I can no longer load FDO binaries from a directory of
my choice, I can only do it from the [application directory].

How could this be?

- Jackie


Hi All,

I've upgraded the FDO binaries in FDO Toolbox from 3.4 RC1 to 3.4 final and
now I always get a System.Runtime.InteropServices.SEHException thrown
whenever I try to get an IProviderRegistry or IConnectionManager reference
from the FeatureAccessManager.

The stack traces I get are:

System.Runtime.InteropServices.SEHException: External Component has thrown
an exception

at FdoFeatureAccessManager.GetConnectionManager() [or
FdoFeatureAccessManager.GetProviderRegistry()]
at OSGeo.FDO.ClientServices.FeatureAccessManager.GetConnectionManager() [or
OSGeo.FDO.ClientServices.FeatureAccessManager.GetProviderRegistry()]
at [whatever method that tries to obtain an IProviderRegistry or
IConnectionManager reference]

Since these two interfaces are basically the gateway to the rest of the FDO
API, FDO Toolbox with 3.4 final binaries is currently broken as it is.

Any ideas?

- Jackie


-- 
View this message in context:
http://n2.nabble.com/FDO-3.4-final-broke-my-toolbox-tp2644748p2644770.html
Sent from the FDO Users mailing list archive at Nabble.com.

_______________________________________________
fdo-users mailing list
fdo-users at lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/fdo-users