disable or configure Fortran IDE extension

[Dandy_E_]

We, numerous colleagues and me, are using Visual Studio 2022 (v17.12.10) with Intel Fortran Compiler 2024.2 installed. The Fortran IDE extension is of version 2021.11.

While editing Fortran code with VS, the editing experience is rather bad:

- we see, often multiple times a day, that editing stops for more than 10 seconds with VS complaining about Fortran IDE is slowing typing performance

- when typing, for instance IF<space>, the input is automatically changed to lower case. Mind that IF was actually typed to get an upper case IF.

- when typing trim( however the input is changed to upper case

Suggestions appear while typing, which is fine, but these seem to be auto-selected and active, and they are automatically applied when <space> or <enter> is pressed. Compare this to editing C code with VS, suggestions are also displayed, but one has to actively select a suggestion via the arrow keys, simply hitting <space> will just insert a space and ignore the suggestions.

There seems to be no way to configure the editing behaviour. Neither is there something in the Tools menu directly, where VS extension usually have their settings, nor does the menu Tools->Options->Text Editor->Fortran have something looking useful, nor did I find anything in %APPDATA% or the oneAPI installation path that resembles something like a configuration file. Searching the online Intel docs and the internet in general revealed no suggestion.

Does anyone know how the editing behaviour can be modified, or how suggestions can be turned of?

[Ron_Green]

There is a newer Fortran Expression Evaluator(FEE) that can be downloaded and installed.  Devorah posted this article that points to this download .

If there is a group of you, choose one lucky person to try installing this newer FEE and kick the tires.  It will obviously work better with the latest 2025.2 compiler for IFX.  But if you are stuck with ifort you may still see some improvements in the debug experience. But no guarantees as ifort is out of support. 

[Dandy_E_]

Thanks for the quick answer.

- I checked and have the latest version of the FEE already installed (VS2025.2.0)

- I disabled the FEE extension: it has no effect on the editing issues, but watching variables while debugging does not work at all (as expected)

Please note that we don't have debugging issues. The original post is concerned with editing problems.

Please note further that ifx from 2025 are unusable under Windows (bogus-floating-point-exceptions-with-ifx-2025-0, ifx-2025-1-fails-under-Windows-with-a-string-macro-defined, while the fix for the latter is not in 2025.2, but expected for 2025.3 in fall 2025).