[fdo-trac] #463: DotNet DLLS should have unmanaged dlls marked as DELAYLOAD

FDO trac_fdo at osgeo.org
Thu Feb 19 11:41:36 EST 2009


#463: DotNet DLLS should have unmanaged dlls marked as DELAYLOAD
-----------------------------+----------------------------------------------
   Reporter:  chriserickson  |       Owner:  gregboone
       Type:  defect         |      Status:  new      
   Priority:  major          |   Milestone:           
  Component:  FDO API        |     Version:  3.4.0    
   Severity:  2              |    Keywords:           
External_id:                 |  
-----------------------------+----------------------------------------------
 When attempting to use FDO 3.4 in a web-service environment, we are having
 to install the unmanaged FDO dlls onto the system path.  This can corrupt
 installations where the user has a different application with a different
 version of FDO installed.

 To resolve this issue, we can modify the web application's path after it
 is loaded, but must have the unmanaged dlls marked as 'delayload' in the
 managed dlls.  This needs to be done on MgCommon, MgFDO, MgGeometry, and
 MgSpatial.  To do so, open up the project properties on each of these,
 navigate to the Configuration Properties\Linker\Input secion, and specify
 each of the dependancies (i.e. FDOCommon.dll on FDO.Common) in the 'Delay
 Loaded DLLs' section.

-- 
Ticket URL: <http://trac.osgeo.org/fdo/ticket/463>
FDO <http://fdo.osgeo.org/>
Feature Data Objects


More information about the fdo-trac mailing list