I am having _exactly_ the same problem you describe and I haven't found any way of working around it. Thanks for the System.Diagnostics.Debugger.Break() tip!!!!!
I've done ALOT of googling on this problem and none of the tips offered have helped. I haven't found any Microsoft articles on it...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.