Hey.
> Ok, please stop - I have no intention of coding something so
> complicated just for a bug that's not even present anymore in the
> latest version of the product (talking about visual studio here).
> Every workaround for the bug in VS2008 just means that there's a
> chance we break an app that does everything right instead.
Well, it's your product of course and you decide. Yet from my experience developing commercial software when MS does something wrong it's not MS problem, it's the developer's problem - noone cares that MS program X does Y wrong, people only care that "damn program doesn't work with MS program X". VS 2008 is still in wide use in many companies although it is not the latest version. This is why I propose a workaround for assessment only - it's likely it is possible to work VS2008 misbehavior around without breaking other programs.
Best wishes.
Dmitry.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2805838
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-07-29 09:12:55 CEST