MS Product Requirements for Future IVF

[jeff_ryman]

This is a question carried over from comp.lang.fortran, since this is probably a more appropriate place.

IFV will require previous installation of Visual C++.NET.
It seems clear that IVF will need the linker and librarian that ship with Visual C++.NET. Will IVF need the Visual C++.NET .LIBS? I ask only out of ignorance about how .NET really works. Are there .LIBS for linking to create .EXEs for .NET and other .LIBS for linking to create .EXEs that don't work under .NET?

[Steven_L_Intel1]

I think you are possibly confused by Microsoft's attaching the .NET name to everything in sight. It would be easier to understand if you thought of MSVC.NET as MSVC7.

In the forseeable future (that means the next year), Intel Fortran will not generate .NET interpreted bytecode. It will continue to generate machine-language object modules, as it (and CVF) does today. The Intel (and Compaq) Fortran libraries have a dependence on the Microsoft Visual C "unmanaged code" libraries, so you need the MSVC libraries as well as the Fortran libraries. CVF installs the MSVC6 libraries (and tools), but, as of this writing, Intel Fortran will not. This means they have to come from somewhere, and the least expensive option is Microsoft Visual C++.NET (7.0) Standard Edition.

We continue to persue the possibility of having Microsoft allow us to include the linker and libraries with our product, so that might change in the future. For now, separate installation should be taken as a requirement. The total cost to the user should be lower overall than it is for CVF.

Steve

[gfthomas8]

Make sure you hold off for VC++.NET 2003. Take a look at

http://www.ondotnet.com/pub/a/dotnet/2002/11/18/everettcpp.html?page=last&x-showcontent=text

Ciao,
Gerry T.

[Steven_L_Intel1]

We already (Intel Fortran 7.1) support VS.NET 2003 (in addition to 2002.)

Steve

[jeff_ryman]

Thank you for your detailed explanation. I was still a little confused from the discussion in clf. I have mixed feelings about MS policies and really don't want to buy any more MS products, but I understand the position Intel finds itself in.

[boronin]

I have a problem using latest Intel Fortran 7.1 with the Visual C++ environment++.NET Standard 2003.
The Visual C quit (or crashes?) completely if I try to run any Fortran code in debug mode, but it runs OK without debugging.

Can anyone help me?

Edouard

[Steven_L_Intel1]

I suggest you submit a problem report to Intel Premier Support. If you haven't already registered, you can do so here.

Steve