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:\windows\system32, 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