cv2pdb: cannot add symbols to module, probably msobj140.dll missing

[Johnson via Digitalmars-d-debugger]

On Monday, 21 August 2017 at 06:16:49 UTC, Rainer Schuetze wrote:
>
>
> On 21.08.2017 05:24, Johnson wrote:
>> On Monday, 21 August 2017 at 03:18:38 UTC, Johnson wrote:
>>> [...]
>> 
>> This just started happening too and a few hours ago I upgraded 
>> VS, so maybe the msobj140.dll changed and broke cv2pdb?  I 
>> copied it to the cv2pdb dir so it should have no trouble 
>> finding it. I've also cleaned the dir. It seems it's doing it 
>> on about everything I change. Going to reboot to see if that 
>> helps.
>> 
>
> Unfortunately, the VS2017 15.3.1 update seems to cause quite 
> some trouble. Bad linker (breaks TLS), bad vcvars*.bat (change 
> current directory), and this issue, too.
>
> I guess they changed something about the (undocumented) 
> interface to the respective DLLs.

;/ That sucks ;/

I guess I might just have to install VS2015, or does that have 
issues too?

Any idea what might be the best VS version that is most 
compatible with Visual D?