| T O P I C R E V I E W |
| znakeeye |
Posted - Mar 02 2008 : 1:56:35 PM
Hi,
The other day I ran into a funny problem.
THE PROBLEM
"WINVER" was defined somewhere, but I could'nt find it - neither in the project settings nor in the source code. So I searched for "WINVER" in all files in Explorer. Yeah, sure... reliable? Naah! Couldn't find **** haha. Sure there are other utilities for this, but the problem remains:
I could not locate the error using Visual Studio.
An experienced programmer soon realizes that "WINVER" must be defined in a certain cpp-file. Great, now you only have to click on each and every cpp-file in the Solution Explorer and check its Properties. The management of compiler settings is simply worthless in Visual Studio. In large projects this becomes very painful. You simply have no control. Still, Microsoft haven't solved it - and probably never will.
THE SOLUTION
VA Outline Pro. When a cpp-file (or any other configurable file) is active, ALL its settings should be viewable in an Outline-like window. Every setting that overrides its project setting should be highlighted. Of course the settings are editable etc. Some kind of overview of all file settings would also be great to have.
I think you get the idea! :)
Perhaps this feature is outside the scope of VAX, but I am quite convinced that whoever implements this will gain an advantage over the competitors. |
| 1 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Mar 03 2008 : 09:58:15 AM
From VA's point of view, this is nearly impossible to do reliably. We have quite a few users who store these settings in UNIX make files, 3rd party compiler configuration files, etc. Places that we know nothing about.
Plus you have the entire problem of DEBUG verses RELEASE settings, which only gets worse when you allow for multiple configurations.
I understand the appeal of this feature, I have encountered similar problems myself over the years. Part of the problem is the number of places settings can be set, and the growing number of ways of doing this.
As soon as you add environment variables, of various types, to the mix then it really starts to get nasty. |
|
|
