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

oneAPI HPC 2022.1 with VS 2022

Jing1
Novice
2,021 Views

Hi,

We recently installed Intel oneAPI HPC 2022.1.0.93 for Visual Studio 2022, we got couple of issues in Visual Studio 2022 with FORTRAN code:

1. If we have a FORTRAN file opened, close VS 2022, then reopen VS2022, we got this error:

Jing1_0-1643917615548.png

 

2. When we debug our FORTRAN code in VS2022, the variables in the watch window won't update, and there are no tooltips for results.

 

Thanks.

 

 

0 Kudos
13 Replies
Steve_Lionel
Honored Contributor III
2,010 Views

The first error happens every time when you left a source file open in the project - annoying. Close the source file pane and reopen the file.

I have not encountered the second problem.

0 Kudos
Jing1
Novice
1,997 Views

Thanks, Steve.

Regarding to the first error, can we say it's a bug in VS2022?

Regarding to the second one, which oneAPI HPC version are you using? Ours is oneAPI HPC 2022.1.0.93.

 

 

0 Kudos
Steve_Lionel
Honored Contributor III
1,988 Views

I don't know where the bug is. I am still on 2022.0.0.161.

JohnNichols
Valued Contributor III
1,977 Views

The bug is likely in the VSIX file developed by Intel for IFX connection to VS 2022.  Fortran is the only language I have found that is having this problem.  VSIX files are not fun to write and given the short time between VS 2022 release and IFX 2022 it is probable that this is the location of the error.  

I would suspect Intel will fix it as they have time to look properly at the VSIX.  I have a VSIX file that only throws an error on one computer with VS2017.  So you can take several weeks to even know you have an error.  

Given the skills of the Intel Moderators I am sure it is reported.  

JohnNichols
Valued Contributor III
1,968 Views

Screenshot 2022-02-03 185405.png
locals work as does watch if you enter the variable name. 

andrew_4619
Honored Contributor III
1,953 Views

Yes watch, locals and quick watch all work but 'hover' does not work most of the time so that really impedes on productivity as the alternatives take more  time. This is a problem as it increases debugging  time (and cost).

Barbara_P_Intel
Employee
1,918 Views

What version of VS2022 are you using?   This article has the VS version supported by oneAPI 2022.1 HPC Toolkit.

 

0 Kudos
andrew_4619
Honored Contributor III
1,909 Views

Microsoft Visual Studio Community 2022 (64-bit) Version 17.0.5 , so from the table do I deduce that is maybe supported maybe not?

 

0 Kudos
Jing1
Novice
1,884 Views

Do you guys know if there is a place where I can submit an official ticket to Intel to fix these issues related to VS2022?

Thanks.

 

 

0 Kudos
JohnNichols
Valued Contributor III
1,873 Views

From a user perspective, you are in the right place, the Intel people monitor this site, these problems I am sure are passed along,  Intel is very good at feedback.  If they need to know more they will ask.  

It just takes time with the development cycle.  Sooner or later all problems are fixed or explained, or in the case of someone like me - ignored for the most part.  

0 Kudos
IanH
Honored Contributor II
1,858 Views
0 Kudos
JohnNichols
Valued Contributor III
1,844 Views

There is a new version of VS 2022 out - I was warned of the upload today, it does not solve the problem. 

0 Kudos
Devorah_H_Intel
Moderator
1,835 Views

@jing  - thank you for your report - we are fixing this issue. 

Reply