forums.silverfrost.com

[AlanFord]

I'm evaluating the use of the FTN95 compiler to convert legacy
Fortran code into applications that can be accessed through ASP.NET
web front-ends.

I am currently working with the evaluation version of FTN95 with plans
to move to the commercial version if everything works well.

One problem though - it appears that, when multiple ASP.NET applications
that use FTN95 are installed on a server, only the first application that
is accessed functions correctly. Accessing subsequent applications results
in an error message of "359: Unable to register class SalfordDialog".
I should note that I'm placing all of the redistributable files in the bin directory
of each ASP.NET application. However, when I move the SALFLIBC.DLL
from each of the application directories to c:windowssystem32, all of the
ASP.NET applications function correctly.

I'm guessing that each ASP.NET application is attempting to load its own
copy of SALFLIBC.DLL and only the "first in" application is successful.
Although placing a single common version of the DLL in the system32
directory is a workaround, this is not terribly desirable as this practice
is frowned upon when I ultimately start working with a production server.

Will this issue go away when I purchase a commercial version of the compiler,
or will I still have to put SALFLIBC.DLL in the system32 directory if I wish
to have multiple ASP.NET applications that access FTN95 .NET compiled dlls?



Thanks for your assistance,
Alan Ford

[PaulLaidler]

I am not familiar with the issues arising with ASP.NET, however, the only difference between the free and the commercial version of FTN95 is that the commercial version does not show a version dialog box when the executable is run. There is no reason (I can think of) why the commercial version should work better with regard to the ASP.NET problem you describe.

[silicondale]

Hi, Alan - it's a few years since you posted your enquiry, so I wondered if you had made any progress, or had given up on it?

I have started from classic ASP and ordinary FTN95 .exe programs (i.e. not using .NET at all) and have got these to work just fine, including production of 2D and 3D graphics. I would really like to migrate to .NET to allow some interactivity within the Fortran applications on the web, and wondered if you could say anything about how to do it - or any pitfalls to avoid. Have you managed to get any Clearwin+ applications running on the web? It would be nice if there were some simple 'prototype' examples available with the compiler, but I haven't found any.

all the best - Steve
_________________
(Steve Henley)

[vspinelli]

this is very very interesting question...
I'm searching a "working" combination of fortran & web ( with no luck..) since 2003.

[silicondale]

hi, vspinelli -

I actually have a working setup on the web using classic ASP and Fortran 95. It uses the Wshell ASP object to launch the Fortran programs, with standard output stream directed to a file, and then the website picks up and displays this once the program has completed. However, must set up all parameters at the start - there's no interaction with the running Fortran program. What I would really really like is something like the Clearwin+ GUI interaction over the Internet. I feel sure this must be feasible, perhaps using the CGI protocol, but not sure how to make it work. Not at all sure whether the .NET framework is likely to help, and if so, whether it would need too much restructuring of existing programs.
regards - Steve
_________________
(Steve Henley)

[vspinelli]

Few years ago lahey released fortran 7.1 with asp form develop http://www.lahey.com/lf71/lfnet.htm
I don't know the reason why Lahey discontinued asp form fortran develop whith newer versions....

regards
Vince