RANT: IVF needs MS VC.NET. What!?

Sigh.

I suppose technically it's my fault for not reading every
single page to do with Intel Visual Fortran before ordering
it. But nobody told me I would need MS Visual C++.Net
(or one of the other MS products that includes the
Visual Studio interface) to run the Intel product.
Yes the information is on the web site. But who thinks
to look for something like that? "Oh, by the way, it
will completely not work unless you have this major
product from another company, a product that is similar
in price to this one."

Maybe I am at fault. But the veins on my forehead are
still throbbing.
Socks

Puppet_Sock wrote:
> Sigh.
>
> I suppose technically it's my fault for not reading every
> single page to do with Intel Visual Fortran before ordering
> it. But nobody told me I would need MS Visual C++.Net
> (or one of the other MS products that includes the
> Visual Studio interface) to run the Intel product.
> Yes the information is on the web site. But who thinks
> to look for something like that? "Oh, by the way, it
> will completely not work unless you have this major
> product from another company, a product that is similar
> in price to this one."

I don't like it either, but I think it suffices to purchase Microsoft
Visual C++ .NET Standard 2003 Edition, which cost only about $100, much
less than Intel Visual Fortran.

beliavsky@aol.com wrote:

> Puppet_Sock wrote: 

> I don't like it either, but I think it suffices to purchase Microsoft
> Visual C++ .NET Standard 2003 Edition, which cost only about $100, much
> less than Intel Visual Fortran.
The x64 version runs currently on free download SDK from Microsoft.
--
Tim Prince

Puppet_Sock wrote:

> Sigh.
>
> I suppose technically it's my fault for not reading every
> single page to do with Intel Visual Fortran before ordering
> it. But nobody told me I would need MS Visual C++.Net
> (or one of the other MS products that includes the
> Visual Studio interface) to run the Intel product.
> Yes the information is on the web site. But who thinks
> to look for something like that? "Oh, by the way, it
> will completely not work unless you have this major
> product from another company, a product that is similar
> in price to this one."
>
> Maybe I am at fault. But the veins on my forehead are
> still throbbing.
> Socks

A friend of mine just switched from Windows XP to Linux because of such
headaches. First time he tried to install the non-commercial version of IFC
for windoze, he was presented with a choice of installing either VS .NET or
VC++ .NET. Naturally, he chose the former. Until the installation program
croaked again complaining about a missing VC++ installation.

He is now happily running ifc (linux) without all this nonsense. And I
daresay that emacs is a lot better and more versatile than anything M$ and
Borland can throw at you.

Tim Prince wrote:

>beliavsky@aol.com wrote:
>
>
> 
>
>
> 
>The x64 version runs currently on free download SDK from Microsoft.
>
>
I got the Windows evaluation version to play with the free "Visual C++
Toolkit 2003", had to edit a few config files and then copy in some
missing library files from the "Platform SDK". It all runs from the
command line, of course. There used to be a page somewhere on Intel's
site discussing this, written by Steve Lionel iirc, can't find it now ...

On Mon, 23 May 2005 19:02:09 GMT, John Doe <jdoe@company.com> wrote:

>I got the Windows evaluation version to play with the free "Visual C++
>Toolkit 2003", had to edit a few config files and then copy in some
>missing library files from the "Platform SDK". It all runs from the
>command line, of course. There used to be a page somewhere on Intel's
>site discussing this, written by Steve Lionel iirc, can't find it now ...

http://softwareforums.intel.com/ids...message.id=8873

Steve Lionel
Software Products Division
Intel Corporation
Nashua, NH

User communities for Intel Software Development Products
http://softwareforums.intel.com/
Intel Fortran Support
http://developer.intel.com/software/products/support/