Always looking for better ways to do things...
- Any and all IDE crashes.
- Intellisense performance. I love the new intellisense features, but it needs a lot of work performance-wise. Imagine Microsoft Word preventing you from typing while the background spell checker is running. That's what it feels like to me.
- The Data Source Configuration Wizard dialog box. If I start typing a name for my new data source, then I suddenly realize "oops, I forgot to select the type of data source object I want..." Selecting the data source type overwrites the name I just wrote!
- Refactoring local variables. This one, maybe I'm missing something fundamental, but it seems like if I'm simply refactoring the name of a local variable, it should run at warp speed. Is it really necessary for the refactoring analysis to run so long? Again, I can only compare the built-in refactoring feature with ReSharper. ReSharper is much faster in this case. So fast, that I don't even notice it.
- Changing control ID values in the Web designer properties window displays a "The Directory Name is Invalid" message box. I'm still working on how to reproduce this error message consistently, but I get it a lot - yes, even running as admin. I end up changing the ID attribute in the source view and avoid the design view as much as possible. Avoiding design view and working almost exclusively in source view is so...VS2003. I was hoping this would be fixed.
- Yet another issue with setting control ID values. Placing a control on a Web form, the smart tag opens up so you can set property values. If you set properties and then return to the property window to set the ID of the control, the refactoring analysis runs. I find this terribly annoying and end up setting the ID in the source view rather than in the design view as mentioned above.
- This isn't really a bug, but more of an annoyance: force the "prop" expansion to place private field declarations at the top of my class. This is something that ReSharper gives me that I miss terribly. Other than that, I love the prop expansion!
- VSS Integration w/ Web sites. I cannot stand the fact that VS tries to include files in the \bin folder in VSS. If you exclude an essembly it renames it .exclude. If you delete the file from VSS, someone else on the team ends up adding it unintentionally. The lack of project files for Web apps is good and bad. The bad: you have to explicitly reference assemblies in the Web.config file and exclude items you don't want referenced in your web project (or do a <clear/>). It will take a little while longer to get used to the new model I suppose.
