Last week was one of those weeks where you feel like you are fighting the tools more than you are writing code. Scott Guthrie was gracious enough to offer help after my temper tantrum about it. :-) Here's what he suggested in case anyone runs into the same issues:
- When the registry setting is set, refactoring will happen with classes within the app_code directory -- but not in any code-behind files (oops, should have read the manual more closely on that one).
- One workaround would be to write a macro that opens the code-behind files for all pages in your web project and then apply the refactoring (this would cause them to be includes as part of the refactoring operation). You could then use this for cases where you know the refactoring will impact pages a lot, but omit running the macro in cases where you think the refactoring is limited to class libraries only.
- An alternative would be to use the new VS 2005 Web Application Project option.
I'll be looking forward to ReShaper 2.0 and VS SP1 for intellisense perf improvements. I just wish these issues were being treated like security flaws in terms of priority. Very selfish, I know. :-)
