Visual D doesn't work, now Visual Studio Code / D doesn't work!!!! ....

[z]

On Sunday, 2 October 2022 at 11:00:06 UTC, Daniel Donnell, Jr 
wrote:
> I thought I set everything up correctly, and now:
>
> ```
> Exception thrown at 0x00007FF7D6E2E230 in metamath-d.exe: 
> 0xC0000096: Privileged instruction.
> Unable to open natvis file 
> 'c:\Users\fruit\.vscode\extensions\webfreak.code-d-0.23.2\dlang-debug\dlang_cpp.natvis'.
> ```
>
> So what the hell do you D developers use to code with if A) 
> Visual D doesn't work - it just ate my app.obj file and can't 
> find it anymore no matter if I clean or re-order the executable 
> paths in settings.
>
> B) VS Code doesn't work out-of-the-box.
>
> Every. Single. Time I get around to using D, there's always 
> something that pops up and doesn't work right.  And it never 
> gets fixed.   How the heck do you expect me to debug without a 
> proper debugging IDE :|

dlang.org seems to implicitly recommends a form of Visual 
Studio(interchangeable with vscodium?), it's recommended enough 
that the DMD(or is it just visual D?) installer proposes to 
install it too.
However, i can confirm that the situation is not that good 
outside of it, most general purpose code editors' D support is 
broken. it seems that implementing support for D is difficult.
Maybe try dexed if it's available on your platform?

If you need debugger badly and VS is inadequate, i can recommend 
x96dbg or another "normal"(not integrated) debugger, it should 
retrieve the debug symbols without difficulty.