- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
My group is looking to upgrade from Compaq Fortran 6.6 to Intel Fortran 10.0. One of the guys has downloaded an evaluation version of Intel Fortran 10. One of the annoying side effect is that a Visual Basic exe with which we run the Fortran DLL gets deleted every time he makes a build. The VB exe is in the debug directory where the DLL gets created.This exe never got deleted under CVF 6.6.
1. Is this deletiongoing to happen with the Non-Evaluation version?
2. If so, is there a way to turn off the "feature"?
Link Copied
1 Reply
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This is the normal behavior of Visual Studio and is not connected to being an evaluation version. When a "Rebuild" of the VB project is done, it deletes all DLLs in its project output folder. If the Fortran DLL was put there in an earlier build, it will get deleted.
I haven't seen this happen when I have two projects in a solution, with dependencies set, and do a Build. The cleaning of the output directories is done first, and then things are built.
Look at the way the provided sample MixedLanguageVB.NET-SafeArrays handles this. The Linker output file property for the DLL project is set to the Bin folder of the VB project and nothing gets incorrectly deleted.
I haven't seen this happen when I have two projects in a solution, with dependencies set, and do a Build. The cleaning of the output directories is done first, and then things are built.
Look at the way the provided sample MixedLanguageVB.NET-SafeArrays handles this. The Linker output file property for the DLL project is set to the Bin folder of the VB project and nothing gets incorrectly deleted.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page