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

VS 2022 Error

JohnNichols
Valued Contributor III
1,203 Views

I have VS 2022 and 2019 installed. 

I have been using a DLL from the Strand7 people, if I do a debug run on 2022 then I get the busy signal 

Screenshot 2023-08-15 174735.png

If I use 2019 I do not 

Screenshot 2023-08-15 174859.png

I cannot send the DLL as it is locked to a dongle, but I tried the stock standard Fortran sample adding a variable X, it does not run on 2022

Screenshot 2023-08-15 175632.png

Windows 11 Preview with latest oneapi on machine.  VS 2022 and VS 2019 are latest.  

0 Kudos
11 Replies
jimdempseyatthecove
Honored Contributor III
1,160 Views

My guess is that a different DLL is being loaded (not Strand7's, possibly one of the .NET DLLs).

In the Debugger, there is an Output Window, not to be confused with the console window (where your PRINT *,... output goes).

In this window, you will see a list of DLL's as they load and unload (plus additional information).

1) Run a test using VS 2019 and break at the return, capture (copy and paste) the contents of the output window (name it 2019.txt)

2) Run a test using VS 2022 and break at the return, capture (copy and paste) the contents of the output window (name it 2022.txt)

Look for differences in paths to the .dll's. If you find a difference, then possibly by modifying you PATH *** inside yor CMD window as oppose to System Environment Variables, you can get your program to work.

: fix.bat
set PATH=PathToDisiredDLL;$(PATH)
YourProgram your args here

 

I have recently (yesterday) run into what I think is the same issue (2022 vs 2019). The error returned to me was a function returning a HANDLE returned a NULL. IOW function failed. No further information.

 

As I am unable to get oneAPI to integrate with 2022 version 17.7.0 (haven't been able to locate version 17.6.4), I had not persued the issue further.

0 Kudos
JohnNichols
Valued Contributor III
1,149 Views

I am using VS2022 17.7.1.  and it happens with the stock standard Intel Template, I just added a variable X and set its value to 1.  And I get the busy signal.  It crashes the program. 

This is likely an intel level problem.  

0 Kudos
jimdempseyatthecove
Honored Contributor III
1,147 Views

The Intel website states support for MS VS 2022 17.6.4

My dowload from MS was 17.7.0, yours is 17.7.1 (don't know why the difference). In any event, this must be related to the integration issue beyond 17.6.4. Apparently, this is not only into the GUI IDE menus, but also runtime break point handling.

 

It would be very helpful, if Intel provided links to the supported versions as opposed to listing the supported version and MS no longer providing (easy to find) links to the older versions. Lack of this stymies prospective users (as well as the more experienced long time users of Intel's products).

 

Jim Dempsey

 

0 Kudos
JohnNichols
Valued Contributor III
1,132 Views

Screenshot 2023-08-16 110047.png

latest versions, if you open the installer it will tell you to update.  

 

MS is on a cycle time of weeks, Intel is on a cycle time of months.  One can of course stay on the MS version listed, but what is the point of life in not riding the bleeding edge of the surfboard.  Or as the guy said the other day in a kayak who hooked a great white, "I think I made a mistake, perhaps I should cut the line".  

0 Kudos
jimdempseyatthecove
Honored Contributor III
1,130 Views

IIF you have NOT installed an (the) working version (for integration with oneAPI), the clicking on the MS website for Community version download does not provide you with the option to select a prior version.

 

:(....

Jim Dempsey

0 Kudos
JohnNichols
Valued Contributor III
1,098 Views

You cannot go back, latest theory from MS.   As my 16 yr old says - trust the process and we are the canaries.  If you want to live a safe life use XP on a machine never connected to the internet.  

0 Kudos
Steve_Lionel
Honored Contributor III
1,109 Views

John, you seem to repeatedly have issues with Preview versions of Visual Studio. Why don't you stick to the production version?

0 Kudos
JohnNichols
Valued Contributor III
1,098 Views

Steve:

I am using the 2019 Version as I need to be able to look at the watch window.  I also have VS 2022 installed, the latest upgrade to this caused an error with Intel Fortran.  I always keep at least 2 versions, so I just use the 2019 and I noted here the problem.   I found the problem cause I started the wrong VS. 

Some one has to be the first into the water, and intel perhaps should know about the problem - the old canary in the coal mine trick.  It is just interesting that is all and Intel needs free canaries. 

VS 2022 preview now integrates with oneapi, but it does not work, but I use preview for some c# stuff.  

I am using stock standard w11 with the latest Nuc11? and they fail terribly in the field, so even production causes problems.  This fail requires a 3000 km drive or an 800USD flight, so there I just use the NUC6 and w10.  My only problem is limited NUC6's. 

John

 

0 Kudos
andrew_4619
Honored Contributor III
1,080 Views

preview: more self inflicted hurt

0 Kudos
AlHill
Super User
1,071 Views

Johnny Cash wrote:

"I hurt myself today
To see if I still feel
 
I focus on the pain
The only thing that's real
 "

 

I think this is what John is saying.

 

Doc (not an Intel employee or contractor)
[Maybe Windows 12 will be better]

0 Kudos
Steve_Lionel
Honored Contributor III
1,065 Views

I have a NUC10 (Windows 11), use it without issue with VS2022 Community and the latest ifort.

0 Kudos
Reply