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

[Johnson via Digitalmars-d-debugger]

On Tuesday, 22 August 2017 at 05:57:20 UTC, Rainer Schuetze wrote:
>
>
> On 22.08.2017 01:27, Johnson wrote:
>> On Monday, 21 August 2017 at 06:16:49 UTC, Rainer Schuetze 
>> wrote:
>>>
>>>
>>> On 21.08.2017 05:24, Johnson wrote:
>>>>[...]
>>>
>>> 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?
>
> VS2013 and VS2015 should both be fine. Building Visual D is 
> also tested on Appveyor for both, too: 
> https://ci.appveyor.com/project/rainers/visuald

Ok, I'll try VS2013. Maybe it will be the most stable. Hopefully 
I can run them side by side without issues.