It starts up every time. It is annoying. I can hide every other tool window, but not this. Why?

I've begun seeing this dialog:

---------------------------
.NET Reflector 7.5 Beta
---------------------------
Don't cry because it's over, smile because it happened.

This early access version has now expired.

Would you like to download now using check for updates?
---------------------------
Yes No
---------------------------

When you click "No", it loads the page! Aargh! How do I get this off of my system? None of the options on the menu seem to do anything anymore.

Also, the "Don't cry because it's over" line is EXTREMELY annoying after the first time. If you're going to get "cute", make sure that you get it RIGHT first.

I really enjoy the Visual Studio integration, but if you need or want to uninstall it for some reason, it can be a bit unintuitive to figure out that you need to open the standalone Reflector, go into the "Visual Studio and Windows Explorer Integration..." menu option and then uncheck the VS checkbox to trigger the uninstall. If it's feasible to add an "Uninstall Visual Studio Add-In..." option in to the .NET Reflector menu in VS, I'd definitely recommend doing that.

Reflector currently does not show the "new" modifier in C# decompilation results (or the similar "Shadows" for VB). This would be quite helpful to see, and it sounds like it could be detected by checking for a NewSlot attribute (see "Caution" box in "Remarks" section of http://msdn.microsoft.com/en-us/library/system.reflection.methodbase.ishidebysig.aspx), which should be relatively cheap as compared to the digging through superclass methods approach that I've seen proposed elsewhere.

The integration in VS2010 is so good, sometimes I am browsing in foreign code without taking really notice of it. It would be good, if decompiled code in VS2010's code editor window would get slightly colorized or otherwise marked to make the difference between own and foreign code clear.

Perhaps there could be a hatched background, or something?...

When decompiling a method that contains an explicit cast to a generic parameter type with a contraint on another generic parameter, the compiler-generated local for the cast is displayed in the decompilation result.

Sample source:

public interface IIdentifiable<TId>
{
TId Id { get; }
}

public class Foo<TItem, TId>
where TItem : IIdentifiable<TId>
{
public Foo()
{
}

public void DoSomething(object target)
{
Console.WriteLine(((TItem)target).Id);
}
}

Reflector decompilation result for Foo<,>.DoSomething:

public void DoSomething(object target)
{
TItem CS$0$0000 = (TItem) target;
Console.WriteLine(CS$0$0000.Id);
}

When the ROB opens on my machine it always has the classic Windows 2000 minimize/maximize/close buttons overlayed on the Visual Studio Chrome. Hovering over them fixes it, but it's quite visible. http://goo.gl/f33GG

Please... Not another tool panel that has no room on my display! If at all possible integrate the Object browser into the Solution Navigator (Dev 11, Visual Studio Power Tools)/Solution Explorer (VS2010). and the standard object browser if at all possible.

It would be great if the Analyzer could find method overrides, either as part of the existing "Used By" list or as part of a new "Overridden By" list.

A picture says more than a thousand words: http://goo.gl/cY67P

When navigating from an Analyzer "used by" or "assigned by" list to a method, I frequently find myself having to use the Find feature within the decompilation window in order to located the actual references to the target member. It would be great if Reflector could do that automatically, say via an additional context menu with a separate shortcut key (e.g.: ctrl+space).

When an Analyzer results list is particularly long, it would be great to be able to filter the list on things like names (or parts thereof) and visibility. Displaying the results in a fancy-pants filterable grid with customizable columns would be a really nice enhancement. (And if you were going to incorporate such a grid, the Search window would be another obvious place to use it.)

When using the Exposed By or Instantiated By analyzer lists, I frequently need to identify the callers of items in the results list. Unfortunately, with the exception of properties, this is a multi-step process that involves manual triggering of the analyzer for the target item. It would be far more convenient if each result item in these lists could be expanded in the same way as items in the Used By results list.

When triggering the Analyze function via a menu or the ctrl+R shortcut, the mouse focus should be automatically transferred to the target item "root" row in the Analyzer window.

It would be great if, when I opt to make something debuggable, the progress of the process is clearly visible, even as I decide to work on something else.

When a missing assembly is identified and the user selects the option to Skip loading then show that assembly in the references section as grey'ed out. When the user moves from one function to another don't reprompt to load the assembly, instead allow the user to later come back and click on the skipped assembly to browse and load it.