The following FAQ answers some of the most common
2024-07-21 02:22:06
供稿：網友
does reflector support xml documentation viewing?
reflector actually includes an xml documentation viewer. select a type, constructor, method, property, field or event and hit the f1 key. the program will either find the documentation file automatically or it will ask for it.
how can i easily figure out what i can possibly do with a selected item?
reflector supports context menus (which can be opened by right-clicking on a node in the browser window). this is often the quickest way to find out what you can do with that item.
how can i view all the information organized by namespace?
reflector supports a namespace-centric mode. here is the trick: open the view menu, click the customize item and enable the "flatten namespaces" checkbox.
why does reflector hold my file locked even after i close it from the file menu?
this is a problem with the clr, not with reflector. right now, the clr does not support an easy way to unload assemblies from memory. even after running "file/close" the runtime still keeps the file in memory. the only way to release the lock is to restart reflector. there are some workarounds for the clr problem but they would all introduce other side effects.
how come i can't find the methods in system.reflection that let me get at the il code?
at the time of writing system.reflection does not support methods for accessing il code. reflector uses its own hand-built exe/dll file reader to read the il code. the routines are exposed, however, in reflector.disassembler for those hard core programmers that want to play around with it.
what is the difference between "file/open" and "file/open name"?
the "file/open name" menu allows you to quickly open files that are already loaded into the global assembly cache (gac). however, when using this option you will find it harder to access the xml documentation that is often stored in the same directory as the original exe/dll. the problem arises because the gac does not provide functionality for navigating back to the original location of an assembly. to avoid that load the exe/dll from its original location.
how do bookmarks work?
the bookmarks tool only works for types, constructors, methods, fields, properties and events at the moment. you can add a selected node to the bookmarks list using the ins key and remove it by pressing del.
how do i use the type search to find a particular type?
type search (f3) shows you all the types available in the loaded assemblies (taking your visibilities settings into consideration). the tool works like a dictionary index and typing syllables in the header boxes is filtering the lower part. the search stops after 1000 elements. you should already have an idea what you are looking for at that point - use filtering to get more. the progess bar at the bottom shows the percentage of the loaded assemblies that is already processed.
how do i use the member search to find a particular member?
member search (f4) works the same way as type search works. it is a bit slower and shows all members as well (types, constructors, methods, fields, properties, events).
what is member references search and why is it so slow?
the member references (shift-f4) tool searches through all of the il code to find all the members that refer to the node that was selected. the member references search tool is very slow at the moment so it can take some time until the search finishes. the search scope is limited for private and internal members. the search can also be made quicker by using the filter and unloading large assemblies which you do not want to search.
what is the difference between the type reference and member reference search?
the type references search shows all the members that refer to the selected type in their meta data. the il code is not searched. this will speed up the search, but may not give you all the results you are looking for.
how do i find out what the various il op-codes do?
move your mouse cursor over the op-code in the disassembler view and wait for the tooltip.
how do i get a call graph? what is the call tree?
the call tree tool shows you a tree of methods that could possibly be called by the selected method. it stops on interfaces and delegates so it is like a compressed nested disassembler view.
how can i view a language-specific definition of a type?
reflector supports a type view which shows the full definition of a selected type node including members in your language of choice. you have to close and restart the type view window after changing the language in the language menu. the view is designed for printing out type definitions (right-click to access the context menu). it can also be used to keep the type definition on the screen while performing additional member navigation. the view is not intended for copy and paste although in many cases it may work.
can i get tooltips based off of the xml documentation while browsing the hierarchy?
no. this feature is not supported in reflector currently, but might be in upcoming versions.
