We have just experienced an issue with the multiple configuration support - mainly that we didn't even know it was there!
A developer added a new configuration - for argument's sake let's call this "Win32 Release Bob". The VBP action for that project was set to build "Win32 Release", but now it builds both configurations - which broke the build when the "Bob" config didn't work.
Looking in the help we discovered that this is intentional; and while a potentially useful feature in some cases; it also can cause problems. This leaves us open to potentially using the wrong build of a project, if for example a developer puts in a test version that matches "Win32 Release".
Is there a way to disable the partial matching and only ever build the named configuration? Other than telling developers not to do it (which won't get remembered after a few months!
)
Thanks.