Distributing apps

[Earl_Geddes]

I build application in VS using VB.net and FORTRAN.  I can always run my code on my own machine or any machine with the Intel FORTRAN compile installed, but I have not had any success in creating a deployment package that will run on a machine without the compiler.

Could someone who has done this run down what is required?

What DLL's must be distributed with my application to use my FORTRAN DLL in the VB.net program?

Obviously the VS deployment Wizard does not work for this example because it knows nothing about the FORTRAN DLL.

Any advice or articles would be greatly appreciated.

Earl Geddes PhD.

President
GedLee LLC

[IanH]

That's the linker command line, not the Fortran compiler command line.  In the properties dialog have a look under Configuration Properties > Fortran > Command line.

(Perhaps you already know this, but...) Visual Studio maintains a solution configuration that is typically Release or Debug (but you can define your own).  It maps that solution configuration through to project specific configurations, that usually have the same name.  You can see that mapping using Build > Configuration Manager.  Similarly there is a solution platform, mapped through to individual project platforms.

Each project has a relatively independent set of properties for each combination of project configuration solution and platform.  Once the properties for a particular combination have been created, if you decide to make a change such as going from dynamic to static runtime libraries, then you need to make that change in each configuration+platform combination.  It is easy enough to forget to do this for a particular combination.

The properties show by default when you first open up the project properties dialog is that which the current solution configuration and platform map to.  Within the dialog you can then edit the properties for different project configuration+platform combinations.  Once you start doing this it is easy enough to get confused between the current combination and your specific selection.

[Earl_Geddes]

Thanks Ian

I did solve the problem.  I am not sure what happened, but given how confusing your description of the configuration was (and yes I knew about that, but didn't realize that it had to be changed everywhere) I am sure that I got it wrong.  I set the project to "Release" for both projects and then the "static" linking for the FORTRAN and it compiled a DLL that runs fine at the clients site.

Thanks again for all your help.