configuration manager in VS 2005 !@$#%
-
I HATE the %!@$# Configuration Manager. Manager? - that's a laugh. And I seem to be able to find no documentation on this anywhere! I added a bunch of different preprocessor options and different configurations to go along with them. But every time a new member of the team gets a sourcesafe version of the project, the configurations aren't there. Well, they're there, but not working correctly. I have to delete them and recreate them, then everything's just fine. Anyone else ever had this problem? My Music | My Pics | My Articles BlackDice
Is it possible that the problem is with SourceSafe, and not VS 2005 ?? Just a guess. ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸
-
I HATE the %!@$# Configuration Manager. Manager? - that's a laugh. And I seem to be able to find no documentation on this anywhere! I added a bunch of different preprocessor options and different configurations to go along with them. But every time a new member of the team gets a sourcesafe version of the project, the configurations aren't there. Well, they're there, but not working correctly. I have to delete them and recreate them, then everything's just fine. Anyone else ever had this problem? My Music | My Pics | My Articles BlackDice
You know, I am with you! I hate VS2005 building process and configuration manager. There is a way to publish to 1 DLL, however I cannot find the way to do it. Now I got in my bin directory hundreds of dlls :(( I want one as VS2003 Al My eMail control My Blog
-
I HATE the %!@$# Configuration Manager. Manager? - that's a laugh. And I seem to be able to find no documentation on this anywhere! I added a bunch of different preprocessor options and different configurations to go along with them. But every time a new member of the team gets a sourcesafe version of the project, the configurations aren't there. Well, they're there, but not working correctly. I have to delete them and recreate them, then everything's just fine. Anyone else ever had this problem? My Music | My Pics | My Articles BlackDice
I don't have VS2005 (just 2003) - but perhaps the configuration options you're having problems with live in user-specific files? Perhaps you've accidentally checked some user-specific files into VSS, and those are overwriting local settings when they are retreived from VSS via a GLV? I may be totally off-base here, but I know I had problems much like you describe when those types of files were accidentally checked into VSS. Caused all manner of bizarre "WTF! I just fixed this 10 minutes ago!"-type errors on GLVs from VSS. The user-specific files I can think of are *.suo (companion to solution files), and *.csproj.user (companion to C# project file). Hope that helps...
-
I HATE the %!@$# Configuration Manager. Manager? - that's a laugh. And I seem to be able to find no documentation on this anywhere! I added a bunch of different preprocessor options and different configurations to go along with them. But every time a new member of the team gets a sourcesafe version of the project, the configurations aren't there. Well, they're there, but not working correctly. I have to delete them and recreate them, then everything's just fine. Anyone else ever had this problem? My Music | My Pics | My Articles BlackDice
-
I HATE the %!@$# Configuration Manager. Manager? - that's a laugh. And I seem to be able to find no documentation on this anywhere! I added a bunch of different preprocessor options and different configurations to go along with them. But every time a new member of the team gets a sourcesafe version of the project, the configurations aren't there. Well, they're there, but not working correctly. I have to delete them and recreate them, then everything's just fine. Anyone else ever had this problem? My Music | My Pics | My Articles BlackDice
Check my blog, I have a post about the VC7.1 config manager. I haven't tried VC 8 but maybe that post will help you anyway.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | NEW!! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
-
Is it possible that the problem is with SourceSafe, and not VS 2005 ?? Just a guess. ø¤º°`°º¤ø,¸¸,ø¤º°`°º¤ø,¸
But wait! MS claimed they re-wrote SourceSafe so that it wouldn't suck! ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
But wait! MS claimed they re-wrote SourceSafe so that it wouldn't suck! ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
John Simmons / outlaw programmer wrote:
But wait! MS claimed they re-wrote SourceSafe so that it wouldn't suck!
:laugh: each new version of Windows is said to be rewrote... and are they really better ? (ok, i conceed, they did a good job when writing NT4)
NT4 was just Win95 with NTFS and a smattering of security considerations. How is that a "good job"? :) ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
NT4 was just Win95 with NTFS and a smattering of security considerations. How is that a "good job"? :) ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
But wait! MS claimed they re-wrote SourceSafe so that it wouldn't suck! ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
Check my blog, I have a post about the VC7.1 config manager. I haven't tried VC 8 but maybe that post will help you anyway.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | NEW!! PimpFish | CP SearchBar v3.0 | C++ Forum FAQ
Haven't tried VC8 yet, but agree about the VC7.1 config manager. The problem seems to come if you have projects within a solution but don't share the same configuration. We've got such a solution and every time we add a new configuration to one of the projects it seems to mess things up. I've had to hand edit the solution file (warning: take a copy first!) to ensure that the mapping from Solution Configuration to Project Configuration is correct. BTW you can set the solution file so that the Debug (Solution) Configuration actually builds the Release (Project) Configuration - totally :evil: Graham
