Answer the question
In order to leave comments, you need to log in
What's the point of Visual Studio filters?
Greetings.
I recently moved back to Visual Studio from another IDE and I had a question: what's the point of filters instead of folders? In conventional IDEs, the project structure is represented by folders and files, while in the studio it is represented by filters .
As a result, in the vast majority of projects (that I have seen), all the files are in the same directory, they are not logically divided in any way, and in order to simply sort through all this garbage, you have to turn on Visual Studio.
I'm not talking about the ahtung that happens when a large library is included in a project, which even purely physically cannot be scattered across all these filters .
What's the point of this? Maybe I don't understand something and my eyes are blurry?
ps I know that there is a "Show all files" button, but it's perfectly clear that by default the studio wants everyone to work with filters.
Answer the question
In order to leave comments, you need to log in
Filters in Visual C++ are a workspace organization technique. This is an old and proven technique that has proven itself in MSVC++ since the very old days.
The filter system allows you to organize any noodles from the files of a third-party library, in which everything is done according to the principle: "Works == Don't touch". This makes her extremely useful.
Filters also allow you to make a finer organization in those places where it is meaningless at the level of the file structure.
I would not be so quick to scold the tool for being used by apparently unorganized or illiterate "specialists". In the vast majority of projects, you just saw ignorance. And nothing more.
Yes, the filters are not tied to real folders in any way, and this is not necessary. Yes, everything can be stored on disk in one folder (and this is the real plus of filters). Yes, filters allow you to organize only within the space of the environment itself.
But nothing more.
Many people do not consider it necessary to separate headers and source code into different folders, blaming the "too complicated" organization of Include Directories. Only this is not a problem of the environment, this is the way people organize their workspace.
I don't know what you mean by filters.
I won't say anything about C++, I write in ASP.NET.
In Solution Explorer, all files and folders included in the project are visible. If you click "Show all files", you can see files and folders that are not included in the project. You can right-click on a file or folder that is not included in the project and in the context menu and select "include in project".
In fact, the programmer thinks over the structure of storing files and folders, even the default organization of storage in the project (Content under css, Scripts under js, bin under dll, etc.) is quite logical and reasonable.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question