DotNet DLLS should have unmanaged dlls marked as DELAYLOAD

[chriserickson]

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.

[ChrisErickson]

This patch includes some extra changes from vista-64 stuff, but mostly just the DELAYLOAD lines are needed.