Annoying MS Visual Studio Professional 2019 behaviour

[gib]

A couple of months ago I upgraded to VS2019 version 16.11.30, having used an earlier version of Intel Visual Fortran for many years with no problems.  I have been putting up with extremely annoying behaviour from VS2019 since switching, and now feel that I have to do something about it.  When editting code there is usually a delay of 2 or 3 seconds between typing characters and seeing them displayed.  It looks as if some sort of checking or logging is being done in the background, but it's hard to understand what could take so much time.  This is with MS Windows 11 on a recent model Dell laptop with an i7 CPU.

I wonder if anybody else has experienced this.  Is there a setting I need to change?

I have attached a text file with the VS2019 info, in case that's useful.

Thanks,

Gib

[Devorah_H_Intel]

Could you supply a Visual Studio solution demonstrating the delay issue for us to test with the latest 2024.1 IFX and Visual Studio 2022?

Is the delay issue you're encountering isolated to a specific project, or is it occurring across all projects built with the 2023.2 version?

The system requirements for Visual Studio 2019 have been provided here. 

[gib]

Hi Devorah,

Thanks for the quick response.

I have been working on a single project from well before I installed VS2019.  The problem occurs while editting code for a DLL, comprising 16 source files, I don't see the delay when I work on the main program, which is a single small file. I'm not keen to send the DLL project unless it's absolutely necessary.  I'll try to create a smaller test project with the same behaviour.

Gib

[gib]

Now here's a funny thing.  I copied the .vsproj file as test.vsproj and all the .f90 files of the DLL project to another directory, and opened test.vsproj with VS2019.  I find that I can edit the source files with no delay!  The build is successful.

What surprises me is that no .sln, ,suo or .u2d files were created in the test directory.  Are these no longer used?  Does that mean I should try deleting those in the original build directory?

[gib]

I have to correct my previous comment.  The .sln and .x2d files were created when I saved the project.  

Still, I wonder if it would be a good idea to close the original project, delete the .sln, .suo and .x2d files then reopen the .vfproj file with VS2019.  Maybe the delay problem is somehow related to my using .sln etc files that were created by a previous VS version - just guessing, I don't recall.

[jimdempseyatthecove]

MS VS generates an Undo/Redo list of your edits that can get quite large.

In addition, the InteliSense feature can get quite large.

I am not sure as to which file type(s) that keep this information (?? *.suo, *.x2d ??)). If you can identify them, deleting them might work.

Yesterday, my edit session bogged down. My edit session with MS VS had been opened and active for over a week (lots of edits).

This time, when I attempted to close out MS VS it hung. After about 10 minutes, I killed it with the TaskManager. Luckily, restarting MS VS with a recover on one of the files, put things back together. This Solution has 20 Projects.

MS goes at its own pace for correcting issues like this. We (Intel Community) can only provide advice on work arounds.

Jim

[gib]

Hi Jim, long time no see.

In fact the .suo and .u2d files are both small, so it's hard to understand how doing anything with these files could take a noticeable amount if time.

I do keep this project open for a long time, many weeks, with many code changes.  It is not clear to me how Intelisense functions.

There is something funny about W11 File Explorer on this laptop.  Sometimes changes made to the file list in a folder (like changing a file name) do not show up until I open a different folder then return to the first one.  This is another annoyance, and possibly related to the VS2019 delay problem.  I don't know of a good place to go for MS Windows help.

It's quite possible that this is a MS problem, not an Intel problem.

Since a copy of the project in another folder does not manifest the delay issue, I guessed that restarting the project from the .vsproj file might at least be a temporary fix.  I closed VS2019, deleted the .suo, .u2d and .sln files, and reopened the .vsproj file.  Now there is no delay.  If the delay problem develops over time, this will be a solution.  It would be nice to know what causes this delay.

Cheers,

Gib

[andrew_4619]

I have experienced this type of edit problem for several years in  VS2019 andVS2022 and maybe VS2017. Several times per day I have to save , exit VS and then open it again. Edit Performance is then restored for a time. I filed a reproducer of one instance (lots of interfaces for a submodule) that demonstrated the problem some months back but I suspect there may be more  than one cause.

Read this: https://community.intel.com/t5/Intel-Fortran-Compiler/Slow-editor-response/m-p/1360712

I am now testing the new release..... Fingers crossed!

[gib]

Hi Andrew,

I'm very pleased to learn that I'm not the only one experiencing this.  It sounds as if Intel is aware of the problem.

It is extremely surprising that a problem like this has existed for so long.  I used VS2005 for many years, and it performed faultlessly.

Life was simpler then.

If and when I start getting delays again, I'll do as you do, close and reopen the project.

Cheers,

Gib

[Andy59]

I also experienced the edit delay problem once but found to be caused by the Source Control extension. After closing the git extension, the delay issue just disappeared.

[gib]

That's interesting.  I have a long list of extensions installed, but Source Control or Git is not on the list.  I see GitHub Extension for Visual Studio available for download, implying that it is not currently there.  The main toolbar does have a Git button, but I assume (hope) that no Git functions are being performed automatically.  There is so much in VS2019 that is obscure to me, having made a huge jump from the simplicity of VS2005.