Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
27427 Discussions

VS 2022 v17.2.x breaks Intel Fortran, use v17.3.2 and newer

Ron_Green
Moderator
11,338 Views

Update 9 August 2022:

  The information, errors, workarounds are for older VS 2022 v17.2.x.  As of 9 August 2022 Visual Studio 2022 v17.3 was released which fixes this issue.

UPGRADE VS2022 to v17.3.0 or newer

 

OLDER 17.2.X INFORMATION

Symptoms:

  • ConsoleFortran.vfproj : error : Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.VisualStudio.Shell.Interop.IVsUpdateSolutionEvents'
  • Project builds fail for existing and new Fortran projects.  
  • Debugger, multiple functions no longer work - breakpoints, examining variables, etc.

 

Affects:   Intel Fortran compiler Integrations into Visual Studio 2022 v17.2.x

Platforms:  Windows only .AND. VS 2022 v17.2.x only (not VS2019 or older).

  • Compilers:  IFORT and IFX versions in
    oneAPI 2022.2 ( ifx v2022.1.0 and ifort v2021.6.0 ) and OLDER
  • Any older Intel Fortran versions than those listed above running under Visual Studio 2022.
  • Does not affect any compilers in VS2019 and older Visual Studios

 

DETAILS:

Microsoft* Visual Studio 2022 (VS 2022) Version 17.2.x  do not work with our Intel Fortran Integrations into Visual Studio in oneAPI 2022.2 and older packages.  This VS version was released on May 10, 2022.  All newer versions of 17.2.x also impacted.  VS 2022 17.3.0 and newer fixes the issue.

Issue:  This update to VS 2022, the 17.2.x , breaks the Intel Fortran Integrations into Visual Studio.  VS 2022 only, not older versions.  IF YOU INSTALL 17.2 and you use packages from oneAPI 2022.2 or older YOU WILL:

  1. NO LONGER BE ABLE TO BUILD EXISTING FORTRAN PROJECTS.  IFORT or IFX
  2. NO LONGER BE ABLE TO CREATE NEW PROJECTS 
  3. Be unable to debug existing executables

 

Upgrade your VS 2022 to 17.3.0 or greater

 

55 Replies
OP1
New Contributor II
722 Views

With Visual Studio 17.3.3 and 17.3.4 the integration of the most recent OneAPI compilers is still buggy: For a solution that consists of fortran projects, each project can be built or rebuilt, but selecting any of the "Project Only" options (Build, Rebuild, Clean, etc.) causes Visual Studio to crash.

So, this is still far from being ready for prime time, I think the original post should be more circumspect about claiming that it works now.

scott_baeder
Beginner
719 Views

Agreed - My current issue is that when re-opening the project, it fails to re-open the files I was working on.  Case filed with Intel support.

 

To me, the gain from better "git" stuff is worth the trade-off...   BUT, yes, still not 100% working (even with the workaround of using the legacy interface)

JohnNichols
Valued Contributor II
702 Views

You are correct, but it is a minor annoyance, and you click on the file and it opens.  

Otherwise it appears to work well. 

Given the number of people who work on these projects, it is a miracle there are so few bugs.  

 

 

tashker__michael
Beginner
556 Views

Thanks for filing a case. Yes, inability to reopen previously open files (VS 17.3.4) is merely a papercut, compared to some errors, but it is moving backwards compared with what Parallel Studio Fortran VS integration offered for so many years.  I hope you sent them a sample screen shot:

An error occurred in 'project_name_blah' while attempting to open 'Read_Parameters.'
File path: c:\blah\blah\Read_Parameters.f90
Frame GUID: 8b382828-6202-11d1-8870-mf87579d2
Frame mode: VSFM MdiChild
Error code Ox8000D4005

(Occurs on 4 machines in different configurations.)

And yeah, selecting any of the Project Only options will kill VS, but luckily I've learned not to do that. But re-opening tabs? It's a feature!

 

regards,

mike

johniou
Novice
548 Views

I can confirm the issue with re-opening a project, where the source files fail to load. You can close them and re-open them, but for some reason VS integration fails to properly load them when a project is first opened.

 

johniou_0-1663953216084.png

 

Ron_Green
Moderator
671 Views
tashker__michael
Beginner
451 Views

Happy to note that oneAPI HPC 2022.3 appears to fix this. The papercut is healing nicely.

g_don
Novice
653 Views

Intel Fortran Compiler (version 2022.1.0) with MVS community 2022 v17.3.2 perfectly work for me both with old projects and with new ones. I suggest you to follow this topic to install only Fortran compiler.

van_der_merwe__ben
New Contributor I
411 Views

I see that Intel® oneAPI HPC Toolkit (version 2022.3.0) has been released which address this issue (see top of forums) but the individual standalone component downloads for Intel Fortran still only offer 2022.2 as the latest (see here https://www.intel.com/content/www/us/en/developer/articles/tool/oneapi-standalone-components.html#fo...). Hopefully that will get addressed soon.

Ron_Green
Moderator
409 Views

Just some confusing versioning.  This comes up often.

The oneAPI 2022 packages started numbering Fortran style at 2022.1. 

The compiler uses its own versioning and we started at 2022.0 so that update 1 was, logically, 2022.1 whereas the oneapi package update 1 containing it was was 2022.2.

The oneAPI 2022 Update 2 package is version 2022.3

The 2022 Update 2 Fortran compiler is 2022.2Next year, 2023, they (oneAPI packaging folks) will get it right and start at zero for the initial release, 2023.0 in synch with our compiler version 2023.0

Version confusion decoder webpage https://www.intel.com/content/www/us/en/developer/articles/technical/oneapi-toolkit-version-to-compi...

 

van_der_merwe__ben
New Contributor I
402 Views

I can confirm that on a clean machine installing Visual Studio 2022 version 17.3.5 and Intel Fortran 2022.2.0.9570 seems to work fine. The Fortran installation proceeded without any issues or needing any workarounds. A solution contain Fortran projects opens and compiles fine.

Ron_Green
Moderator
406 Views

added a post on versions in 2022 HERE

van_der_merwe__ben
New Contributor I
394 Views

On machines where you already have have Intel Fortran Classic 2022.0.0.77 installed along with VS 2022 17.3.5, if you try and install the new version 2022.2, you may get this:

Removal of component has failed.

Component id: intel.oneapi.win.compilers-common.ide.common_vs2022, name: IDE Common for Visual Studio 2022.0.0-161.

Error: Sequence execution failed.

This happens if you have previously replaced Microsoft.VisualStudio.Setup.Configuration.Native.dll with a different version to install an older Intel Fortran version and you neglected to restore the original dll after.

van_der_merwe__ben
New Contributor I
386 Views

This is caused by replacing that one VS DLL that prevented installation of an older Intel compiler, so most people will not encounter this.

Reply