Visual D bug in paths

[Jo Blow]

On Wednesday, 30 March 2022 at 16:52:35 UTC, Rainer Schuetze 
wrote:
>
>
> On 26/03/2022 05:54, Jo Blow wrote:
>> On Friday, 25 March 2022 at 09:18:09 UTC, Rainer Schuetze 
>> wrote:
>>> 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?
>> 
>> The exact error is a dialog that pops up saying:
>> 
>> "
>> cannot launch debugger on
>> C:\projects\test\test\Win32\Debug\test.exe
>> hr = 800702e4
>> "
>
> The error code means "The requested operation requires 
> elevation.". I guess that there might be some compatibility 
> concerns regarding the windows version built into the 
> executable.
>
> I suspect you are building the programs with the Digital Mars 
> toolchain (which uses the OMF object fileformat and the optlink 
> linker). Try enabling MS-COFF output on the Compiler->Output 
> project configuration page.
>
It was checked, I tried unchecking and using various debuggers 
but all the same issue.

I tried removing the requests library and commenting out all the 
code except main and it's return but same thing.

I copied the code to a new project and it works fine(can debug) 
so this seems to be something to do with a setting/configuration 
between the projects. I've compared the project settings and they 
are identical(having two VS's open on the settings pages and 
switching back and forth. Only thing different is the copy 
command on post-build).