forums.silverfrost.com

I'm glad you got it to work.

I just want to comment that it seems like you were confused about the differences between a Win32 DLL and a .NET DLL. In .NET, you don't need to include all of the Dec ...

Well, it's been years since I posted this and made it work; I ultimately dropped trying to reuse old Fortran code and spent the time to convert everything to VB (things worked in VB2008, but I couldn' ...

I have the need to update a .NET application that I wrote in Visual Basic 2008 Express a couple years ago that calls a Win32 DLL that I compiled using Silverfrost FTN95 Express. The problem quickly a ...

I figured out how to bring in the .NET dll and add a reference to it in the VB.NET project. So far, so good.

Tim

I had been compiling the DLL in Win32 mode, so I tried to switch to .NET mode since I am trying to call this from Visual Basic.NET. However, when I switch the FTN95 compiler/linker options to .NET DL ...

Originally being Fortran 77 code, the Intent attribute wasn't used, and not be overly experienced in Fortran, I had never heard of if. However, at your suggestion, I just tried it... it made no diffe ...

I've got some old (originally Fortran 77) subroutines that I've converted into a DLL that I am calling from Visual Basic 2008.NET SP1. I pass it several variables (some integers, floating points and ...

Entering this in the Extra Linker Options (in Visual Studio) is exactly what I was looking for, and had tried, but I had the syntax wrong. I didn't realize that I had to put a dash ("-") in ...

I've built a Win32 DLL that contains several internal subroutines and functions, and everything appears to be working fine. In the Linker options, I've answered "Yes" to "Export All&qu ...