Good refactoring tool
-
Do you have any suggestions for any refactoring tool ? The one which comes with VS is not good. It made my application unusable. I renamed a class using VS refactoring tool. It renamed all references. But when I compiled, I came to know that it's not updating the references written in ASPX (no cs page) pages. Then I have to manually find for the class name and replace. Stupid tool
All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions
-
Do you have any suggestions for any refactoring tool ? The one which comes with VS is not good. It made my application unusable. I renamed a class using VS refactoring tool. It renamed all references. But when I compiled, I came to know that it's not updating the references written in ASPX (no cs page) pages. Then I have to manually find for the class name and replace. Stupid tool
All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions
I've used ReSharper before now, it's not bad.
I'm largely language agnostic
After a while they all bug me :doh:
-
Do you have any suggestions for any refactoring tool ? The one which comes with VS is not good. It made my application unusable. I renamed a class using VS refactoring tool. It renamed all references. But when I compiled, I came to know that it's not updating the references written in ASPX (no cs page) pages. Then I have to manually find for the class name and replace. Stupid tool
All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions
Your brain.
-
I've used ReSharper before now, it's not bad.
I'm largely language agnostic
After a while they all bug me :doh:
-
Your brain.
digital man wrote:
Your brain.
I know someone voted you down because it is a pain to do everything by scratch... but I voted 5 for specific reasons. Even if you use a tool to assist in refactoring, knowing exactly WHAT that tool is doing for every option you choose is priceless knowledge. Things often break when you don't understand the risk involved in the operation you are doing, or the implications to the complexity of your application. I am often reminded of the old "replace all" which was the very first refactor that got everyone in trouble. A rename operation seems sooooo easy, but when done with an editor's "replace all" function is so inherently dangerous that it should always be done with a bit of forethought before hitting that button. The brain, the knowledge of how something works whether you are doing it from scratch or using a tool to help you, is extremely important. Now if only I could get mine to work before coffee.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
-
Do you have any suggestions for any refactoring tool ? The one which comes with VS is not good. It made my application unusable. I renamed a class using VS refactoring tool. It renamed all references. But when I compiled, I came to know that it's not updating the references written in ASPX (no cs page) pages. Then I have to manually find for the class name and replace. Stupid tool
All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions
-
digital man wrote:
Your brain.
I know someone voted you down because it is a pain to do everything by scratch... but I voted 5 for specific reasons. Even if you use a tool to assist in refactoring, knowing exactly WHAT that tool is doing for every option you choose is priceless knowledge. Things often break when you don't understand the risk involved in the operation you are doing, or the implications to the complexity of your application. I am often reminded of the old "replace all" which was the very first refactor that got everyone in trouble. A rename operation seems sooooo easy, but when done with an editor's "replace all" function is so inherently dangerous that it should always be done with a bit of forethought before hitting that button. The brain, the knowledge of how something works whether you are doing it from scratch or using a tool to help you, is extremely important. Now if only I could get mine to work before coffee.
_________________________ Asu no koto o ieba, tenjo de nezumi ga warau. Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
I almost never take that approach. Much better to rename the member and then compile, you get a nice annotated list of what to fix.
I'm largely language agnostic
After a while they all bug me :doh:
-
I almost never take that approach. Much better to rename the member and then compile, you get a nice annotated list of what to fix.
I'm largely language agnostic
After a while they all bug me :doh:
I'm (very) old school and still prefer to use my eyes and my brain when coding (still hand carve all markup, etc). Also, if you need to constantly refactor you've got bigger problems anyway. Just the way I was taught.
-
I've used that recently too, it gets a thumbs up from me.... although I wouldn't personally shell out pennies for it, it wasn't THAT good (trial version available on their website)
-
Do you have any suggestions for any refactoring tool ? The one which comes with VS is not good. It made my application unusable. I renamed a class using VS refactoring tool. It renamed all references. But when I compiled, I came to know that it's not updating the references written in ASPX (no cs page) pages. Then I have to manually find for the class name and replace. Stupid tool
All C# applications should call Application.Quit(); in the beginning to avoid any .NET problems.- Unclyclopedia How to use google | Ask smart questions
Don't use the wrong name in the first place..... If you design the code first they you can refactor all day on the design and implement once you are sorted.