Running under the debugger of Visual Studio 2008 ever thing works fine.
Either a web service or WCF service (coded in C#) can dllimport and successfully run either a Fortran DLL (that exports) or that same DLL packaged as a COM server (registered by regsvr32 and accessed via a NET generated reference thereof).
Outside of the debugger there are problems. The invocation occurs, i.e. the DLL is imported and the entry point invoked, or the COM class is created and the interface invoked (using the COM reference ), but after that the service dies. This seems to be related to a lack of trust of the unmanaged FORTRAN by IIS. These problems cannot be conquered using element in the config file.
So it seems like I should use the tlbimp.exe with the appropriate switches to create a strongly named assemblyfrom the INTEL FORTRAN generated COM Server. Does that seem reasonable? Is there another way without resorting to COM?
Anyone else solved the challenge of deploying a web service or WCF (wsHTTPBinding) that invokes FORTRAN DLL or COM Server?
