Visual Studio has encountered an exception.

[Glenn1]

I have VS2010 installed on 2WINDOWS 7 64-bit systems. I have just updated the fortran compiler on both systems from "w_fcompxe_novsshell_2011.5.221" to "w_fcompxe_novsshell_2011.7.258". The updates appeared to install without a hitch. However, on both systems, I get the following error when I open the solution (double-click the .vfproj file): "Visual Studio has encountered an exception. This may be caused by an extension. You can get more info...."

Has anyone else encountered this and resolved it? If so, what is the resolution?

Thanks!

[Wendy_Doerner__Intel]

The fix should be in the Composer XE Update 8 just posted this week. Can you try installing it from registrationcenter.intel.com to see if it resolves the issue?

------

Wendy

Attaching or including files in a post

[bbeyer]

I have just installed Composer Update 8 on Windows 7 and am still getting the same exception described above. I have been closing the error message box and continuing without any apparent problems for the past several months, but would like to eliminate the error if possible. Any ideas?

Bill

[Steven_L_Intel1]

Try this. Uninstall Fortran. Delete the "Intel Fortran" folder under Microsoft Visual Studio 10. Reinstall Fortran.

[Jon_D]

Installing update 8, or uninstalling and re-installing IVF didn't help me in my case. The solution that I kept getting the error with had 8 Fortran projects. It turned out that some of the projects were created by VS 2005 they weren't converted to VS 2010 format. I opened each of the projects by themselves and converted to VS 2010. This solved my problem.

Jon

[Glenn1]

I uninstalled all fortran compilers, reinstalled only "w_fcompxe_novsshell_2011.8.278.exe" and still encounter the same exception message. The only thing that seems to prevent the exception from occurring in my case is to rename (or remove) the associated solution file (.sln) and then launch my project.I don't get the exception when I do this. I can then rename the solution back to the original name and launch without the exception occurring.

I have three projects each with an associated solution that has produuced the exception until I perform the steps I just mentioned above. The exception has not occurred again - yet.