Now I know why people use makefiles
-
Although this is a Visual Studio specific thing, it seems this forum (based on the help info from the website) is for Visual C++ questions/issues. Visual Studio project handling has gone so far downhill since 6.0, it's astounding. Once again, I've been stupidly bitten by the thinking I can apply an All Config/All Target parameter (preprocessor directive in this case) forgetting that it will blow away all the other carefully crafted per Config/Target values. This seems so stupid, I feel I must be missing something obvious? I mean, if I change something project wide like precompiled headers, it doesn't destroy the individual file settings. Has VS v9 really lost the ability to properly handle file/config/target/global settings like preprocessor directives? Please tell me there is something obvious that I should click/check/choose in order to have a global item simply be added, rather than something so remarkably wrong as removing all the specific items and replacing them? Sorry if this sounds like a rant, but I just lost ALL the target specific settings for all 6 projects in my solution because I had to add _CRT_SECURE_NO_WARNINGS to all targets/configs. I have them in SVN, but still, there were other changes I've made tonight that I will lose. And given how advanced VS v9 is, it seems insane that I'd need to wear out my mouse battery with all the individual clicking and pasting that doing it one at a time would take. Thank goodness for :1,$s/(XX)/\1;YY/ in vim... But why has this gotten so very, very wrong since VS v6? Hoping to find out I've just stupidly overlooked something,
-
Although this is a Visual Studio specific thing, it seems this forum (based on the help info from the website) is for Visual C++ questions/issues. Visual Studio project handling has gone so far downhill since 6.0, it's astounding. Once again, I've been stupidly bitten by the thinking I can apply an All Config/All Target parameter (preprocessor directive in this case) forgetting that it will blow away all the other carefully crafted per Config/Target values. This seems so stupid, I feel I must be missing something obvious? I mean, if I change something project wide like precompiled headers, it doesn't destroy the individual file settings. Has VS v9 really lost the ability to properly handle file/config/target/global settings like preprocessor directives? Please tell me there is something obvious that I should click/check/choose in order to have a global item simply be added, rather than something so remarkably wrong as removing all the specific items and replacing them? Sorry if this sounds like a rant, but I just lost ALL the target specific settings for all 6 projects in my solution because I had to add _CRT_SECURE_NO_WARNINGS to all targets/configs. I have them in SVN, but still, there were other changes I've made tonight that I will lose. And given how advanced VS v9 is, it seems insane that I'd need to wear out my mouse battery with all the individual clicking and pasting that doing it one at a time would take. Thank goodness for :1,$s/(XX)/\1;YY/ in vim... But why has this gotten so very, very wrong since VS v6? Hoping to find out I've just stupidly overlooked something,
Craig Longman wrote:
I just lost ALL the target specific settings for all 6 projects in my solution because I had to add _CRT_SECURE_NO_WARNINGS to all targets/configs.
I don't know why this happened to you but I have got many projects with individual and independent file, config, etc settings, which I can change without problem. This has worked for me through the Visual Studio Express Editions 2005, 2008, and 2010. BTW there is a Visual Studio specific forum.
I must get a clever new signature for 2011.
-
Craig Longman wrote:
I just lost ALL the target specific settings for all 6 projects in my solution because I had to add _CRT_SECURE_NO_WARNINGS to all targets/configs.
I don't know why this happened to you but I have got many projects with individual and independent file, config, etc settings, which I can change without problem. This has worked for me through the Visual Studio Express Editions 2005, 2008, and 2010. BTW there is a Visual Studio specific forum.
I must get a clever new signature for 2011.
Even with only one project, in VS v9, if I select all targets/platforms and put in a preprocessor directive, it simply removes all the current directives and replaces it with what I typed in. This doesn't happen this way for you? Sorry about the wrong forum, I looked, but the closest I saw was this one having a description of "C, Visual C++ and MFC" and thought it was the closest.
-
Even with only one project, in VS v9, if I select all targets/platforms and put in a preprocessor directive, it simply removes all the current directives and replaces it with what I typed in. This doesn't happen this way for you? Sorry about the wrong forum, I looked, but the closest I saw was this one having a description of "C, Visual C++ and MFC" and thought it was the closest.
Craig Longman wrote:
it simply removes all the current directives and replaces it with what I typed in.
I just tried that in Visual C++ Express 2010 and it works fine, the new value gets added but nothing gets deleted.
Craig Longman wrote:
I looked, but the closest I saw was this one having a description of "C, Visual C++
Hmmm, I would have thought that "Visual Studio" is closest; this question has almost nothing to do with C, C++ or MFC.
I must get a clever new signature for 2011.
-
Although this is a Visual Studio specific thing, it seems this forum (based on the help info from the website) is for Visual C++ questions/issues. Visual Studio project handling has gone so far downhill since 6.0, it's astounding. Once again, I've been stupidly bitten by the thinking I can apply an All Config/All Target parameter (preprocessor directive in this case) forgetting that it will blow away all the other carefully crafted per Config/Target values. This seems so stupid, I feel I must be missing something obvious? I mean, if I change something project wide like precompiled headers, it doesn't destroy the individual file settings. Has VS v9 really lost the ability to properly handle file/config/target/global settings like preprocessor directives? Please tell me there is something obvious that I should click/check/choose in order to have a global item simply be added, rather than something so remarkably wrong as removing all the specific items and replacing them? Sorry if this sounds like a rant, but I just lost ALL the target specific settings for all 6 projects in my solution because I had to add _CRT_SECURE_NO_WARNINGS to all targets/configs. I have them in SVN, but still, there were other changes I've made tonight that I will lose. And given how advanced VS v9 is, it seems insane that I'd need to wear out my mouse battery with all the individual clicking and pasting that doing it one at a time would take. Thank goodness for :1,$s/(XX)/\1;YY/ in vim... But why has this gotten so very, very wrong since VS v6? Hoping to find out I've just stupidly overlooked something,
It's not just you. What's crazy is if you copy preprocessor settings from another project and paste them, it's smart enough to remove duplicates!
-
Craig Longman wrote:
it simply removes all the current directives and replaces it with what I typed in.
I just tried that in Visual C++ Express 2010 and it works fine, the new value gets added but nothing gets deleted.
Craig Longman wrote:
I looked, but the closest I saw was this one having a description of "C, Visual C++
Hmmm, I would have thought that "Visual Studio" is closest; this question has almost nothing to do with C, C++ or MFC.
I must get a clever new signature for 2011.
I just did it again in v9 and when All Configurations is selected, it replaces them all. I guess it was fixed.
Richard MacCutchan wrote:
Hmmm, I would have thought that "Visual Studio" is closest; this question has almost nothing to do with C, C++ or MFC.
Indeed, I guess I didn't actually point out that the Visual Studio way at the bottom escaped my attention. =) Thanks anyway, clearly something resolved in the next version, another good reason to upgrade I guess. Just gotta be careful for the time being.