Comments
4 comments
-
Yep, this is intended behaviour. We have piggybacked on Visual Studio's ability to produce metadata when you choose to "Go to definition" on an item in code.
Unfortunately, we couldn't find a way to suppress the metadata view appearing briefly during this process, which causes the effect you see.
Thanks for the report, -
Perhaps I was having wrong expectations then
I was hoping that this command will load the reflected source code in Visual Studio without opening Reflector at all (only use its API to reflect the source). Could I request this as a new feature? -
What you ask for is a feature of reflector pro. If you decompile an assembly (using the "Choose assemblies to debug" dialog) F12 and right click>go to definition will have this behaviour.
Cheers, -
Nice!
Thank you for your prompt replies!
Add comment
Please sign in to leave a comment.
I am experiencing some strange behavior when using the official beta of ReflectorPro. When I choose the "Open in .NET Reflector" command in Visual Studio 2008 the generated source code file is automatically closed after a few seconds and Reflector opens up. Is this expected?
I have prepared a video showing my experience: http://screencast.com/t/NDkwYTFkNG