All Forums  Visual Assist  Feature Requests  Refactor Export Class

You must be registered to post a reply.
Click here to register.

Screensize: 640 x 480 800 x 600 1024 x 768 1280 x 1024 UserName: Password: Format: Font Andale Mono Arial Arial Black Book Antiqua Century Gothic Comic Sans MS Courier New Georgia Impact Lucida Console Script MT Bold Stencil Tahoma Times New Roman Trebuchet MS Verdana   Size 1 2 3 4 5 6   Color Black Blue Brown Green Red Violet Yellow Message: Forum code is on. Html is off. [quote][i]Originally posted by sl@sh[/i] [br]Currently I am busy trying to adopt parts of a project's base structure to up-to-date techniques. What I have are heaps of structs and functions. What I want is a hierarchical structure of classes and methods. The problem I have is that I cannot afford to just throw everything away, I need to do a gradual change. This means my first steps usually consist of changing the keyword 'struct' to 'class', provide getters and setters (not all, just those that make sense), and let the compiler tell me where the problems are. Once I am at the stage that a newly converted class works, I would like to 'export' it into an individual file - for one to cut it's ties to dozens of other structs and function declarations that share the same header, and also to make sure I've covered all the dependencies (and of course because I consider it bad style to put more than one class into one header/implementation file). The problem I have at this point is that VS 2003 does not provide helpful functions for that task: first, it always wants to put the class header and implementation files into my project's base folder (and that, exactly, is the place I want none of the files except for some chosen few), and changing the folder alone is a PITA! Second, if I try to create aclass using file names to match the class name, VS tells me that a class of that name already exists! (of course it does - that's why I want to create those files in the first place!). Alternately I can create a new header and implementation file seperately, doubling the number of steps needed (again, changing the directory is a PITA. Twice!). People might suggest that I should create the class files before I even change the struct to a class, but unfortunately that wouldn't work very well - for one I often change class names as an afterthought, and changing the according file names appropriately is - you might guess it - another PITA. What's more, it sometimes turns out that I need to split up a struct into several classes, or combine several structs into one. For that reason I defer creation of the actual class definition files to a point where I'm sure the class is mostly final. The solution I am hoping for would be a new refactoring method from VA. I would require something that enabled me to shove a class definition from an existing header file to a newly created one, preferably matching the name of the class, and within a directory I am able to choose in a reasonable way (i. e. not the way the VS dialog handles this: it only lets you type in the complete path or choose an already existing(!) file(wtf?) with the help of a file dialog). At the same time, shoving class method definitions from an existing file to a newly created one (again, using the class name) should be available aas a refactoring method. I realize the latter will be harder, but maybe it could be realized using VA Outline. Sorry for the long post, but this is an issue that really bothers me - even to the point that I decided to spend halve an hour writing all this... [/quote]   Check to include your profile signature. Check to subscribe to this topic.