By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
434,961 Members | 2,492 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 434,961 IT Pros & Developers. It's quick & easy.

Adding a new project in sourcesafe breaks the build!

P: n/a
Anyone know why?:

When someone adds a new project in sourcesafe, even though it only
exists as a hierarchy of folders and subfolders beneath the main
solution but is NOT REFERENCED either in a solution ( project, dll
reference or otherwise), visual studio 2005 in its great wisdom (or even
msbuild when building outside of the IDE) FINDS IT!?!

I dont have any "*"'s in the build script, and in the solution it brings
up warnings relating to this arbritrary project even though NOTHING in
the open solution referes to it (I've even used grep, in my madness).
It's sole existance appears to be the reason for it being picked up and,
bizarly, BUILT.

Is this a known issue/behaviour/mannerism/feature/bug? What is causing
this. Obviously when some developer comes along and creates a new
project and it breaks the build its not happy days.

Any insight that can save me from darkness that ensues each time this
happens would be greatly, if not overly appreciated.
Sep 30 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.