Refactoring a module into a class: Changing shared fields to instance fields?

Here is the way I would go about changing this. For every field in GlobalDefinitions do the following Use Visual Studio Refactor Rename to rename it to a unique name Bad_Name_a This will turn all of the hard to match names into very easy to match names Do a global search and replace for Bad_Name_a to globalDefinitionsInstance. Bad_Name_a No need for even a regex here.

The name and replacement are unique Use Visual Studio Refactor Rename to rename it to the better name of your choosing.

Here is the way I would go about changing this. For every field in GlobalDefinitions do the following Use Visual Studio Refactor Rename to rename it to a unique name Bad_Name_a. This will turn all of the hard to match names into very easy to match names Do a global search and replace for Bad_Name_a to globalDefinitionsInstance.

Bad_Name_a. No need for even a regex here. The name and replacement are unique Use Visual Studio Refactor Rename to rename it to the better name of your choosing.

Thank you. It will still be a lot of work, but at least safer than a simple search & replace. – christian studer Nov 15 at 7:40.

I would first use the built-in VS 2010 rename functionality to rename a to something that is as unique as possible, such as ReplaceThisSillyPropertyNameNow. Then you can do a global search and replace on the new name with your desired replacement.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.