Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
FPGA community forums and blogs on community.intel.com are migrating to the new Altera Community and are read-only. For urgent support needs during this transition, please visit the FPGA Design Resources page or contact an Altera Authorized Distributor.
29285 Discussions

Deploying Fortran DLL with .NET

jcbarnett
Beginner
‎07-10-2008 01:33 PM
725 Views

I am building a C# .net application that calls a DLL built with Visual Fortran 10.0 using Visual Studio 2005.The deployment is via ClickOnceand the applicationruns under Windows XP.The installation puts the Fortran DLLin the exe folder and copiesdforrt.dll filetosystem32. On a development machine, the application runs fine fromthe installation, buton a client machine, reports an error that it cannotfind the specified Fortran module. Other DLL's, built with Visual C++ 6.0,also reside in the exe directory and are found, so I suspect it is a dependency problem. What otherfiles need to be distributed with the application for a .NET installation? Is any special setup needed for deploying and running the Fortran DLL with .NET?

-jcb

0 Kudos

Link Copied

1 Reply
Steven_L_Intel1
Employee
‎07-10-2008 05:46 PM
725 Views
dforrt.dll is a CVF DLL, not used by Intel Visual Fortran. Use Dependency Walker to see which DLLs your DLL uses. Alternatively, build your Fortran DLL against the static libraries. If there is no other Fortran code in the application, that's reasonable.
0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.