How can we help you today? How can we help you today?
Bitterman

Activity overview

Latest activity by Bitterman

Many thanks Jessica. Things seem to be working pretty well now on the whole, but those extra feature requests you mention would certainly make for a better all-round experience. Thanks again. / comments
Many thanks Jessica. Things seem to be working pretty well now on the whole, but those extra feature requests you mention would certainly make for a better all-round experience. Thanks again.
0 votes
"GoTo Definition (F12)", "Track Loaded Modules", "Disable Just My Code on startup" and "Decompile From Call Stack" are all enabled (ticked) in the .NET Reflector menu. Is there an option to send in an error report when this error occurs? If so, can you kindly send one in and enter your email as bitterman@forums.com so that we can find it and check the stack trace leading up to the error? Can I also please check, if you manually go to the cache in %userprofile%AppDataLocalRed Gate.NET Reflector 8Cache, do you see all the pdbs for the assemblies you've selected? I set it to "Generate PDBs" again and started typing an update in this browser window... while I was typing, an error dialog appeared and took focus, and just as I pressed the space bar, it interpreted that as a button press and closed Visual Studio! (Didn't see if it was an error from Reflector or VS itself). So I went back to do it for a third time, and this time it showed the cache as considerably larger than 2 MB (now 727 MB)... it seems the second attempt had at least partially succeeded before the error occurred. I checked the location you mention, and there are now lots of PDBs (and some decompiled CS files) there. Anyway, as there were still a few that hadn't been cached, I set it to generate the cache again, and it crashed again, so I sent the error report to the address you mention. Hope it helps. In summary, "Generate PDBs" now seems to have at least partially succeeded, whereas at the first attempt it failed completely. As a result, I'm now getting much better results for the other problems: I am now getting Reflector decompiled code whenever I use F12, debugging external code is working properly, and debugging async/await code is working properly. It seems that the initial failure to Generate PDBs caused all of those problems, and I'm much happier now. That just leaves a couple of concerns: - Is the initial failure to Generate PDBs likely to cause longer-term problems? (eg. if I need to generate more, for other DLLs, later?) Hopefully the error report should help determine this, it may be that it's fine from now on. - Couldn't Reflector be a bit "smarter" / more reactive in terms of when to Generate PDBs? ie. if I haven't already generated a particular PDB, I'd hope it would do it "just in time" when I attempt to debug into it... it may not always be clear which assemblies will need to be debugged, until it's time to debug them. If that had been the case, I might never have noticed a problem. Am I expecting too much? - The code generated by Reflector's F12 still does not contain any comments from XML documentation. Picking an example from the first page of code I'm looking at: pressing F12 on string.Replace(...) takes me to the Reflector decompiled code for that method in mscorlib.dll, including an attribute, but with no comments. However, leaving the cursor on string.Replace(...) and viewing the Visual Studio Code Definition Window shows me the method signature (no code of course), but also the comments from XML (Summary, Parameters, Returns, etc). When the XML documentation is available, it should surely be used by Reflector? Many thanks for your help. / comments
"GoTo Definition (F12)", "Track Loaded Modules", "Disable Just My Code on startup" and "Decompile From Call Stack" are all enabled (ticked) in the .NET Reflector menu. Is there an option to send i...
0 votes
.NET Reflector problems in VS2013
I previously had .NET Reflector 7 working fine with VS2010 on my old PC. Now that I've bought a new PC, I am trying to get .NET Reflector 8 working with VS2013 but it's having some trouble. 1. When...
2 followers 8 comments 0 votes