CVF 6.6 and C#.NET

sabalan · ‎02-20-2004

I have a customer who uses object files compiled by my CVF 6.6 in a DLL workspace, to build his own DLL. Now he wants to migrate all his own code from Fortran and VB to C#.NET. Does anybody know:

1- Can he use the existing object files right away and just CALL and link them with his new C# code?

2- If yes, has any specific measures to be taken for COMMONs which were used both in my object files and his code to make them work even between C# and CVF object files?

3- If no, how and with which compiler should my code be compiled?

I knownothing about C#, and not much about .NET.

BTW, searching C# in the forum finds all C++!

Sabalan.

Message Edited by Sabalan on 02-20-2004 05:29 AM

sabalan · ‎02-24-2004

OK. The situation, and the question, has changed. The customer wants my code to be compiled in .NET environment (MSIL) ONLY and nothing else. Then I have to choose either Lahey's Fortran.NET or Salford's FTN95 for .NET.

Does anybody know which one of these requires less pain to migrate CVF code to?

Sabalan.

Message Edited by Sabalan on 02-24-2004 01:07 AM

edmund_dunlop · ‎02-24-2004

Sabalan

I have tried the Lahey download and subsequently bought Salford's FTN95. The performance of FTN95.NET is much better than that of Lahey.NET ( see www.polyhedron.com ). My main reason for choosing FTN95 in the end however was that, in my opinion, it is a lot easier to adapt legacy code than with its competitor - and the product better fits totraditional Fortran mindset and skills. I am quite happy with my purchase.

Although the performance of FTN95 is quite good - I must agree with Steve Lionel's remarks in an earlier posting: Quote -"It is not clear to me what benefit you see from shifting to .NET interpreted code - it doesn't gain you any portability to 64-bit platforms over a compiled code 32-bit executable, and is likely to be a lot slower (and require the end user to install the .NET Framework, which narrows the set of Windows variants the code can run on.)"I am further of the view that the best option for the most painless development of Fortran apps with GUI is the combination of IVF (given further CVF support/development is finishing) and the excellent Winteracter. You might still be able to argue a case with your customer.

Best wishes,

Edmund.

sabalan · ‎02-25-2004

Thanks Edmund for your message.

I agree with you and with Steve regarding unclear benefits in shifting to .NET and don't know why the customer wants to make this shifting. I will try to show him disadvantages of it, but I have to follow his decision anyway because "the customer is always right", you know!

Sabalan.

Message Edited by Sabalan on 03-01-2004 12:57 AM