Visual D bug in paths

[Jo at blow.net]

I had issues with old projects working correctly after upgrading 
to 2022.

The issue is that the "Debug source files" point to 2019 which 
were deleted upon upgrade.

That is, right mouse button on the project Solution in the 
Solution Explorer and click properties. Then go to Common 
Properties -> Debug Source Files. A new project uses ..\Microsoft 
Visual Studio\2022\Enterprise\... ...14.30... while the old 
projects point to ..\Microsoft Visual Studio\2019\Enterprise\... 
... 14.25...

And this gives an issue debugging the old project. I'm pretty 
sure the 2019 files don't even exist any more. IIRC I uninstalled 
everything having to do with VS before upgrading.

The issue is that there is no easy way to update the projects to 
get them to work.

My specific issue is that I could not debug the x86 project 
because it would give an error: "Cannot launch debugger on" which 
does not occur on creating a new x86 project(which led me to 
snooping around and seeing that the "debug source files" where 
different and the old one was pointing to the hold files.

I tried find a way to fix this but I couldn't. I think it must be 
using a pointer to something.

I guess a solution would be to detect those files and see if they 
exist and/or compare them to a new version and ask the user if he 
wants to upgrade the project or have a link in the visual d menu 
that can be used to update the project?