- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Greetings,
I've delayed migrating from CVF 6.6 to Intel because, frankly,the conversion processscared me. I'm now revisiting the issue and want to be certain I have it right. So far, it still scares me...
The old 2005 white paper (pdf) stated that the user must have installed MS Visual C++.NET or MS Visual Studio.NET (version 02 or 03) with the Visual C++ component installed. Now, I see that Intel 11 comes packaged with MS Visual Studio 2005 Premier Edition. Sounds good, except for the fact that The Knowledge Base article states that the wizards for converting CVF Projects into Intel 11 Solutions aren't available in that version of Visual Studio. That seems to indicate that if you want the conversion process to go well, you still need to buy MS Visual Studio 2008. Is that correct? If so, why does Intel 11 come with a Visual Studio version that lacks that key migration feature?
Also, the old white paper said you needed to have the Visual C++ component installed for things to work. Is that still required as another separate purchase from Visual Studio 2008, or is the C++ component included therein?
Thanks for your help!
Albert Harting
I've delayed migrating from CVF 6.6 to Intel because, frankly,the conversion processscared me. I'm now revisiting the issue and want to be certain I have it right. So far, it still scares me...
The old 2005 white paper (pdf) stated that the user must have installed MS Visual C++.NET or MS Visual Studio.NET (version 02 or 03) with the Visual C++ component installed. Now, I see that Intel 11 comes packaged with MS Visual Studio 2005 Premier Edition. Sounds good, except for the fact that The Knowledge Base article states that the wizards for converting CVF Projects into Intel 11 Solutions aren't available in that version of Visual Studio. That seems to indicate that if you want the conversion process to go well, you still need to buy MS Visual Studio 2008. Is that correct? If so, why does Intel 11 come with a Visual Studio version that lacks that key migration feature?
Also, the old white paper said you needed to have the Visual C++ component installed for things to work. Is that still required as another separate purchase from Visual Studio 2008, or is the C++ component included therein?
Thanks for your help!
Albert Harting
Link Copied
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The problem for the CVF project converter is that it depends on Visual Studio to convert a "VC6" project (which is what a CVF project looks like to the project system) to a current Visual C++ project. The "Extract Compact Visual Fortran Project Items" wizard then works from that and pulls out the Fortran information. The VC project converter is part of the Microsoft C++ product and not licensed to us as part of the "Visual Studio Premier Partner Edition" (VSPPE).
So if you want to have CVF projects converted automatically, you need to have the actual Visual C++ installed and not the bundled Visual Studio Premier Partner Edition. The workaround I would recommend, which is really not all that difficult unless you have made a lot of customizations, is to create a new project and add your source files to it.
The requirement for the Visual C++ component is only for users who are relying on a separately purchased Visual Studio. We call that out because Visual Studio has many components, such as VB or VC# and those other components will not satisfy Intel Fortran. If you are using the bundled VSPPE, then it has everything needed and you don't need to worry about it.
We're here to help you if you get stuck. Tens of thousands of CVF users have already made the switch, you can too.
So if you want to have CVF projects converted automatically, you need to have the actual Visual C++ installed and not the bundled Visual Studio Premier Partner Edition. The workaround I would recommend, which is really not all that difficult unless you have made a lot of customizations, is to create a new project and add your source files to it.
The requirement for the Visual C++ component is only for users who are relying on a separately purchased Visual Studio. We call that out because Visual Studio has many components, such as VB or VC# and those other components will not satisfy Intel Fortran. If you are using the bundled VSPPE, then it has everything needed and you don't need to worry about it.
We're here to help you if you get stuck. Tens of thousands of CVF users have already made the switch, you can too.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Quoting - Steve Lionel (Intel)
The problem for the CVF project converter is that it depends on Visual Studio to convert a "VC6" project (which is what a CVF project looks like to the project system) to a current Visual C++ project. The "Extract Compact Visual Fortran Project Items" wizard then works from that and pulls out the Fortran information. The VC project converter is part of the Microsoft C++ product and not licensed to us as part of the "Visual Studio Premier Partner Edition" (VSPPE).
So if you want to have CVF projects converted automatically, you need to have the actual Visual C++ installed and not the bundled Visual Studio Premier Partner Edition. The workaround I would recommend, which is really not all that difficult unless you have made a lot of customizations, is to create a new project and add your source files to it.
The requirement for the Visual C++ component is only for users who are relying on a separately purchased Visual Studio. We call that out because Visual Studio has many components, such as VB or VC# and those other components will not satisfy Intel Fortran. If you are using the bundled VSPPE, then it has everything needed and you don't need to worry about it.
We're here to help you if you get stuck. Tens of thousands of CVF users have already made the switch, you can too.
So if you want to have CVF projects converted automatically, you need to have the actual Visual C++ installed and not the bundled Visual Studio Premier Partner Edition. The workaround I would recommend, which is really not all that difficult unless you have made a lot of customizations, is to create a new project and add your source files to it.
The requirement for the Visual C++ component is only for users who are relying on a separately purchased Visual Studio. We call that out because Visual Studio has many components, such as VB or VC# and those other components will not satisfy Intel Fortran. If you are using the bundled VSPPE, then it has everything needed and you don't need to worry about it.
We're here to help you if you get stuck. Tens of thousands of CVF users have already made the switch, you can too.
Thanks for the reply, Steve.
I think I follow you, but just to be sure:
If I DO elect to purchase a separate Visual Studio (VS 2008, I assume) so that I have the automatic conversion utility, I will need to buy Visual C++ and install that into Visual Studio. Oddly, I don't find Visual C++ listed as a separate product at Programmer's Paradise, but I do see it as a download directly from MS. Is that the normal way to obtain that component?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No... If you buy Visual Studio (2008 Standard Edition will be fine) and you choose the "typical" install, you'll get C++ included automatically. The mention of C++ is there to alert those who might decide to do a custom install and keep only, say, Visual Basic. If you do choose a custom install, make sure that C++ is selected.
If you will be developing for the Intel 64 (x64) platform, and you have purchased Visual Studio Professional Edition (or higher), you will need to do a Custom install and make sure that the "x64 compiler and tools" option is selected under C++ - it isn't by default. The Standard Edition installs the x64 support by default.
If you will be developing for the Intel 64 (x64) platform, and you have purchased Visual Studio Professional Edition (or higher), you will need to do a Custom install and make sure that the "x64 compiler and tools" option is selected under C++ - it isn't by default. The Standard Edition installs the x64 support by default.

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page