I am currently porting an application from Visual C++6.0 to Visual Studio .Net 2003 and struggling a bit with the IDE, trying to get back to being productive.

With VC++6.0 it was possible to organize the Class View into folders within each project. This made it fairly convenient to work with a project with hundreds of classes. It allowed filtering out the classes exposed by 3rd party OCX's, etc by placing them in a subdirectory. It allowed one to maintain an organized hierarchical view of the project. When new classes were introduced, it was obvious that they were not yet placed in the hierarchy. Heck, the Code Project even had a utility to save and restore the class view when the old IDE would occassionally lose its mind and forget the entire thing.

With VS.Net 2003 it doesn't seem possible to use the Class View to create this organized view. It seems like virtual folders can only be created outside of the projects. And since the classes are not removed from there original location when you drag them from a project, it would be challenging to create and maintain an entire organized class view in virtual folders.

How do VS.Net 2003 users working with large legacy MFC applications use this Class View effectively?

Thanks for any guidance available.