From your complaints… An update on the bugs filed


"urn:schemas-microsoft-com:office:office" />HTML/XML
editor does not support incremental search in a read-only file.

Still active, we are hoping to fix this.

 

Request for seperate font settings for Memory
debugger toolwindow

This has been fixed in recent Whidbey builds!

 

navigating to task list items in collapsed
regions is annoying

Still active. I hope we fix it.

 

Task list request to allow default views to
stay the default

We’re going to improve the task list filtering in Whidbey and make it more usable
and less aggravating.  (I’m paraphrasing
our PM)

 

Editor Back and Forward should listen to Mouse
navigation keys

Still active. I’m also pushing for this.

 

Asp.NET user request for “Copy File” Command

From our Project Team PM “There is an easy
workaround to this – you can either copy the file in the solution explorer or copy
the file on disk.”


 

User Request for one time “Sync to Solution
explorer”

Would be nice, but we won’t be able to get to it in Whidbey.  Keep
your fingers crossed for future versions or powertoys. J


 

Customer request for history in property pages

Postponed. No time from the debugger team. But they like the suggestion.

 

View.NavigateBackward should remember scroll
position as well as caret position

Still active. Fingers crossed that we get to it. 

Comments (1)

  1. MartinJ says:

    You know, I forgot about a few from before. I know that these probably won’t make into Whidbey, but…

    When including a reference to a .com object, apply a strong name *IF* the project in question is strong named. This would prevent me from having to go to the command line and build a wrapper assembly with a strong name.

    Add the option to install a windows service from the IDE on the dev machine. I thought it was there in 1.0, and couldn’t find it in 1.1. I thought it showed up as a custom action in the designer (like how you can add an installer class when viewing a service in the designer).

    Don’t split HTML begin/end tags when you use self closing syntax. I’ve seen the designer decide it needs to change <TAG /> to <TAG></TAG>. Then, IE can render the HTML incorrect since it didn’t expect to see that closing tag. I notice that the HtmlTextWriter class doesn’t have this problem (if you close a tag with no inner text, it renders it as a self closer).

    I’m sure that there are more. I just can’t think of them right now.

    -Martin