Mixed language DLL support outside the IDE?

D

David Short

I'm missing something fairly easy.

I've a mixed language application running c# and DLL's of C++ and Fortran
code. The application works fine on the machine with the development
environment. Microsoft's C compiler and Intel's Fortran compiler. The target
machine and the development machines both have .Net 2 on them

If I copy over the directory to a separate machine, the executable
crashes/throws exceptions as the first non c# DLL is accessed.
If I create a setup project to install the new application on a separate
machine, the same thing happens.

Pointers to what I've missed would be well received.

dfs
 
J

JoeW

I'm missing something fairly easy.

I've a mixed language application running c# and DLL's of C++ and Fortran
code. The application works fine on the machine with the development
environment. Microsoft's C compiler and Intel's Fortran compiler. The target
machine and the development machines both have .Net 2 on them

If I copy over the directory to a separate machine, the executable
crashes/throws exceptions as the first non c# DLL is accessed.
If I create a setup project to install the new application on a separate
machine, the same thing happens.

Pointers to what I've missed would be well received.

dfs

I'm no expert but off the top of my head would the DLLs have to
registered via regsvr32 first?
 
?

=?ISO-8859-1?Q?Arne_Vajh=F8j?=

JoeW said:
I'm no expert but off the top of my head would the DLLs have to
registered via regsvr32 first?

If COM DLL's not if Win32 DLL's.

Arne
 
?

=?ISO-8859-1?Q?Arne_Vajh=F8j?=

David said:
I'm missing something fairly easy.

I've a mixed language application running c# and DLL's of C++ and Fortran
code. The application works fine on the machine with the development
environment. Microsoft's C compiler and Intel's Fortran compiler. The target
machine and the development machines both have .Net 2 on them

If I copy over the directory to a separate machine, the executable
crashes/throws exceptions as the first non c# DLL is accessed.
If I create a setup project to install the new application on a separate
machine, the same thing happens.

Pointers to what I've missed would be well received.

Does the DLL's you produce depend on some DLL's that
comes with either compiler or other apps installed
on the development machine ?

Arne
 
D

David Short

Arne Vajhøj said:
Does the DLL's you produce depend on some DLL's that
comes with either compiler or other apps installed
on the development machine ?

They are indeed w32 dll's. How can I check DLL dependencies?

dfs
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top