On 1 September 2013 18:49, Walter Bright <newshound2@digitalmars.com> wrote:

On 9/1/2013 1:06 AM, Benjamin Thaut wrote:

Also if you are using Visual Studio 2012, you need to change the debugging
engine because the new one can't deal with D code that has C++ debugging info.

This endless merry-go-round of MSC breaking the tools constantly is why I went with my own toolset years ago.

And I don't blame you, but sadly, to achieve success in the Windows environment, I'm absolutely convinced it must work seamlessly with the de facto standard MS infrastructure.