Visual D bug in paths

[Rainer Schuetze]

On 21/03/2022 21:38, Jo at blow.net wrote:
> So I deleted the .vs directory and it fixed the debug source files so 
> they now point to the 2022 install. I still cannot debug the old project 
> in x86 mode even after messing with various debuggers(mago, mixed mode, 
> visual studio). I've tried matching up the new working projects settings 
> with the old and everything is the same so I have no idea what really is 
> going on.
> 
> 


AFAICT the "debug source files" usually only contain the directories of 
the Microsoft C++ header and source files. More directories are added 
there if you manually locate a source file that the debugger cannot find 
autoamtically.

I don't see an update of those directories when loading a solution into 
VS 2022, even with VS 2019 still installed, so deleting the .vs folder 
seems like a good solution. I don't think these settings are vital to 
starting the debugger, though.

I guess you are using the visualdproj projects. The "mago debug engine" 
that can be selected in the debugging options is a 32-bit engine only, 
so it doesn't work in VS 2022 anymore. The "mago extension" to the 
Visual Studio debugger is ported to 64-bit and works with both VS 
engines adding similar and more functionality.

One thing I stumble over from time to time is that the VS project 
configuration dialog doesn't always open with the current configuration, 
so changes to the settings seem to have no effect.

If that doesn't help: what is the exact error message you get?