need Visual Studio 2010?

[skinner__karl]

Hi, I need advice please

I recently purchased Intel Fortran to co-work with collegues in Sweden. I subsequentlty found out that they use VS2005 whilts Fortran ships with VS2008. Furthermore my collegues are to upgrade to VS2010.Will the two versions (2008 & 2010) be compatible, ie. can we share common project files?
If not, will I have to buy VS2010 or is there another way of getting it? I did not expectthis extra expense when I started using Intel Fortran.

thanks
karl skinner (Siemens)

[Steven_L_Intel1]

If you are sharing the .vfproj files, then you don't need to be on the same VS version, but the .sln solution files won't be compatible. I don't know of an alternative other than buying the same VS version.

[skinner__karl]

Thanks Steve for your reply - bad news though it is.

Are there plans to ship Intel Fortran with Visual Studio 2010 in the near future that I could upgrade to? If not, I have tofind some $600to buyVS2010.

I correct in thinking I need the VS Professional Edition?

[Steven_L_Intel1]

Yes, we are intending to switch to the VS2010 shell, but that won't be until a future major release. For VS2010, yes, the Professional Edition will do.

[Andrew_Smith]

There are several versions of VS2010 Express that are free. Would any of these do?

[TimP]

VS Express won't enable you to use project or .sln files at all with ifort, so doesn't appear to satisfy your requests.

[Steven_L_Intel1]

Microsoft does not allow non-MS tools to integrate into the Express Editions.

[Jugoslav_Dujic]

Quoting kskinn

Thanks Steve for your reply - bad news though it is.

Are there plans to ship Intel Fortran with Visual Studio 2010 in the near future that I could upgrade to? If not, I have tofind some $600to buyVS2010.

I correct in thinking I need the VS Professional Edition?

But why don't you just maintain two separate .sln files? Unless you add or remove projects from it on a regular basis, they don't change often. It's not the most convenient solution, but hey, it saves you some bucks.

I'm not particularly happy with VS2010. The new features aren't worth the cost of new bugs (lack of IntelliSense for C++/CLI), or well-maintained old ones (I have a list of a dozen minor annoyances from VS2008 which were just carried on into VS2010). And it's slow, needless to say.

[Steven_L_Intel1]

I agree with Jugoslav that VS2010 is a step backwards in many ways.