Lately, I've been refactoring a C# WinForms application that ported from VB6 via a commercial converter. Let's just say the resulting code wasn't pretty. As a result, I've been refactoring the heck out of it. I'm down about 3000 lines of code to date. Nice.
This morning, I decided to change the namespace. I used Visual Studio's refactoring tool to perform the rename. Love it. Then, I start getting this error:
I search everywhere. There's absolutely no evidence of this previous namespace in the code. Where is this guy? Finally, I re-read the error more carefully and decide to check Project Properties. Yep, sure enough, the StartUp object is still using the old namespace:
Ok, so I'm operating a little slowly this morning. My bad. However, how come VS.Net couldn't have included Startup object in the rename refactoring? Further, how about throwing the Monday morning developer a bone and simply direct me to look at the Startup object. Appreciate it.
This morning, I decided to change the namespace. I used Visual Studio's refactoring tool to perform the rename. Love it. Then, I start getting this error:
I search everywhere. There's absolutely no evidence of this previous namespace in the code. Where is this guy? Finally, I re-read the error more carefully and decide to check Project Properties. Yep, sure enough, the StartUp object is still using the old namespace:
Ok, so I'm operating a little slowly this morning. My bad. However, how come VS.Net couldn't have included Startup object in the rename refactoring? Further, how about throwing the Monday morning developer a bone and simply direct me to look at the Startup object. Appreciate it.
Comments