Intel® Fortran Expression Evaluator (FEE) installation

[GBOND]

I use Intel compiler fortran with VS for 15 years now . 

But I have difficulties to use the the debugger with IFX version.

 I understand  i have to  install Intel® Fortran Expression Evaluator (FEE) extension manually 

Can you explain the procedure to install it? Thank you.

[MarcGrodent]

From Visual Studio select the "Extensions" menu, then "Manage Extensions" => type "intel fortran expression evaluator" to search for the extension and install it.

There is an interesting discussion here about the FEE:

https://community.intel.com/t5/Intel-Fortran-Compiler/Will-Intel-Fortran-Expression-Evaluator-2025-1-work-with-with/m-p/1695844 

[GBOND]

Thank you, it is done.

Nethertheless, I have still troubles for the allocated tables  .

 In the specification of the intel Fortran Expression it is written: 

"The Intel® Fortran Expression Evaluator allows developers to:

• Evaluate Fortran expressions during debugging. (ok for me)
• Check the values of variables or compute custom expressions on-the-fly. (ok for me, it must be in UPPER CASE , ok)
• Support array slicing, derived types, and some Fortran intrinsic functions (e.g. ALLOCATED, ASSOCIATED, LOC) ." (not ok for me).

Maybe i have forgotten something or there is a restriction , or  i need probably to install something else?

A simple example below: impossible to read the value Tab_XY

[MarcGrodent]

It works for me even in lower case (although tab_xy is displayed in upper case in the Watch window).

I'm using Visual Studio Community 2022 version 17.14.20 and ifx 2025.3.0

[GBOND]

Seeing your results, as it didn't work on my own pc, so i tried on a new pc with nothing  installed on it and effectively it works now. 

Thus I decided  to desintall the Intel products on my pc (it was not sufficient)  and to desintall  either Visual Studio 2022 completely.

I reinstall everything: 

Visual Studio Community 2022 version 17.14.20

and

compiler ifx  2025.3.1.15

and

The Intel® Fortran Expression Evaluator 2025.2.2

and now it works 

I think there was  probably a conflict with a previous version not completely deleted.

Anyway, thank you for your help.

[MarcGrodent]

Good to know!

Yes, upgrading to the last versions of VS and IFX is generally the good option.