Comments
4 comments
-
Yes, I'd be really interested to get the assembly that causes that crash. I've sent you an email.
Thanks a lot, -
dll + project sent by e-mail
-
That was good fun to debug. Unfortunately, I'm not going to be able to fix it completely, as the function (the constructor of PCDataContext) is just too large, and causes a stack overflow. It's not worth rewriting to avoid the recursive walking the contents of the method, but I've put in something to avoid crashing VS completely. It'll be in the next build.
Thanks, -
That's fine; for insane code, simply reporting an error (rather than killing VSTS) seems reasonable. And yes: that generated code is pure evil, but great for test purposes ;-p
Add comment
Please sign in to leave a comment.
I have a sample dll that I wanted to decompile (oddly enough, so I could re-compile it and use with source in ANTS) - it gets to 68% and then hard-crashes VSTS. (I repeated the attempt, just in case it was karma).
I can supply the dll on request. The dll is my own, and is not obfuscated. It is actually generated on-the-fly (CSharpCodeProvider) from data; I was simply trying to use Reflector to save myself the trouble of going in, turning on debug (so that it writes the cs to disk in addition to the dll), re-deploying and re-building the dynamic portion. I can supply the referenced dlls if needed, and the original cs if that would be helpful.