I have a complex C / C ++ application group that I am working on, and which should also be platform independent. It is still compatible with UNIX / Windows and works fine. However, supporting this monster on VS2010 is a nightmare. I have the following file structure:
/
sources
lib1
include
...
src
...
lib2
include
...
src
...
app3
include
...
src
...
builders
cmake
...
make
...
VS2010
vs2010.sln
lib1
lib1.vcxproj
lib1.vcxproj.filters
lib2
lib2.vcxproj
lib2.vcxproj.filters
app3
app3.vcxproj
app3.vcxproj.filters
As we can see, since everyone is platform independent, I had to completely separate the builders from the sources. IMHO, this in itself is a very good practice, and this should be respected by everyone :)
Here's the problem now ... VS2010 is completely unusable when you have to organize include / sources files in filters. You must do this manually by re-doing โAdd โ New Filterโ and then โAdd โ Output Elementโ. I have a VERY complex folder structure and files in each included folder. The task of creating filters becomes a full day job. On the other hand, I could just drag the entire folder from Explorer to the project inside VS2010, but all the header / source files will be placed there without any filters, which makes it useless: you cannot search in 100 files for the correct one without hierarchy .
Question: Is VS2010 any obscure way to import a folder AND save the folder structure as filters? It seems to me that the M $ FT people who created VS2010 believe that M $ FT is the only animal in the jungle, and you MUST contaminate the source folder with building projects so you can use "show hiden files" to turn them on into the project along with the folder structure. This is absurd IMHO ...
source share