[fdo-users] Delay loading dlls ?
mbranscum at agvance.net
Mon Dec 13 12:36:47 EST 2010
It sounds like you may be running into the same issue I ran into a while back while deploying FDO in ASP. Are you saying that you had to add your FDO ASP app's bin folder to the $PATH in order to get the native DLLs loaded?
That is what we initially had to do. However, if I remember correctly I think we eventually put the FDO DLLs in their own directory and then added only that directory to the system path. That way we didn't have to add the ASP app's bin folder to the system path and risk the side effects you are describing. However, that approach has the side effect that all ASP applications on the server will need to use the same FDO DLLs and you would not be able to run multiple versions of FDO. But that was not an issue for us.
From: fdo-users-bounces at lists.osgeo.org [mailto:fdo-users-bounces at lists.osgeo.org] On Behalf Of Oyvind Idland
Sent: Monday, December 13, 2010 9:18 AM
To: fdo-users at lists.osgeo.org
Subject: [fdo-users] Delay loading dlls ?
we have an issue with dll loading when using them in an Asp.NET application.
The server pre-loads assemblies before executing the app. While doing this, it will also attempt to load
native dependencies. Deployment and loading works somewhat different in an Asp application, so
its starts looking for the dll's all over the place. In some cases it may load dll's from another app's
bin-folder, if it is set in $PATH.. which causes unpredictable consequences in some cases.
If delay load is set on the topmost dependencies, the Asp-app can specify the dll using SetDllDirectory()
before the dependencies is loaded.
Is it possible to have this feature added in FDO 3.5 and above ?
-- Øyvind Idland
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fdo-users