MSbuild question - how to tell items in .ggroupproj to
compile release

I have thus far had an outstanding conversion of our companies BDS 2006 
products over to bds 2007 (great job Codegear). Even got the ceeFIT 
libraries and Devexpress libraries compiled and working great. Now I need 
some MSBuild help (the documentation seems very sparse). I have a project 
group .groupproj file containing numerous projects. Using the commandline 
(automated build system) how do i tell MSBuild to build all those projects 
in either debug or release mode? I am able to do this for individual 
projects using

/t:Build /p:Configuration=Release
/t:Build /p:Configuration=Debug

But it does NOT seem to work for .groupproj files. I see the default active 
project is used when called from a groupproj and don't know how to override 
this behaviour? (Canadian spelling :))

Thanks

-- 
Mark Vejvoda
web: www.soft-haus.com
blog: www.soft-haus.com/blog 

Ok I found the solution (and it also applies to individual project files). 
The proper way to toggle debug and release (proper in that through my 
experimentation it is the only mechanism that seems to work) is to use the 
following commandlines:

msbuild.exe myprojgroup.groupproj /t:Clean;Build /p:"Config=Release
Build"
msbuild.exe myprojgroup.groupproj /t:Clean;Build /p:"Config=Debug
Build"

msbuild.exe myproj.cbpproj /t:Clean;Build /p:"Config=Release Build"
msbuild.exe myproj.cbproj /t:Clean;Build /p:"Config=Debug Build"

Thus far I have to say that RAD Studio 2007 is an excellent product. Finally 
I have some hope to work in a stable C++ IDE. I was quite skeptical to 
upgrade from BDS2006 as my experience from BCB6 -> 2006 was absolutely 
hideous. Good job Codegear, you have started to earn back some trust from 
me. I also think that switching to MSBuild is basically a dream come true 
for any serious C++ customers out there that use Rad Studio. In our
"Agile" 
team we totally rely on automation and reliable builds. This was problematic 
in BDS2006 with a very flaky build system.

"Mark Vejvoda" <mark_vejvoda@hotmail.com> wrote in message 
news:47796a07$1@newsgroups.borland.com...
>I have thus far had an outstanding conversion of our companies BDS 2006 
>products over to bds 2007 (great job Codegear). Even got the ceeFIT 
>libraries and Devexpress libraries compiled and working great. Now I need 
>some MSBuild help (the documentation seems very sparse). I have a project 
>group .groupproj file containing numerous projects. Using the commandline 
>(automated build system) how do i tell MSBuild to build all those projects 
>in either debug or release mode? I am able to do this for individual 
>projects using
>
> /t:Build /p:Configuration=Release
> /t:Build /p:Configuration=Debug
>
> But it does NOT seem to work for .groupproj files. I see the default 
> active project is used when called from a groupproj and don't know how to 
> override this behaviour? (Canadian spelling :))
>
> Thanks
>
> -- 
> Mark Vejvoda
> web: www.soft-haus.com
> blog: www.soft-haus.com/blog
> 

"Mark Vejvoda" <mark_vejvoda@hotmail.com> wrote in message 
news:477a6111$1@newsgroups.borland.com...

> Thus far I have to say that RAD Studio 2007 is an excellent product. 
> Finally I have some hope to work in a stable C++ IDE. I was quite 
> skeptical to upgrade from BDS2006 as my experience from BCB6 -> 2006 was

> absolutely hideous.

Agreed.

> Good job Codegear, you have started to earn back some trust from me. I 
> also think that switching to MSBuild is basically a dream come true for 
> any serious C++ customers out there that use Rad Studio. In our
"Agile" 
> team we totally rely on automation and reliable builds. This was 
> problematic in BDS2006 with a very flaky build system.

Unfortunately, RAD Studio has its own build problems problems.  Try to 
specify the output path for certain file types and you will discover that 
you either can't specify them (HPP), or they won't go where you want (BPI). 
Build events can be used as a workaround, but it's a hack for a common bug 
in every C++Builder product since day one.  I wish they would concentrate 
more effort in this area.

- Dennis 

In article <47796a07$1@newsgroups.borland.com>,
 "Mark Vejvoda" <mark_vejvoda@hotmail.com> wrote:

> But it does NOT seem to work for .groupproj files. I see the default active

> project is used when called from a groupproj and don't know how to override

> this behaviour? (Canadian spelling :))

msbuild.exe ProjectGroup.groupproj /t:MakeAll (or BuildAll, or CleanAll)

should make/build/clean all configurations (Debug, Release, and any 
custom ones you have created)

If you only want to do Release or some custom configuration that is not 
set as the default, then the solution you posted appears to be the 
correct answer.
-- 
David Dean (CodeGear)

In article <477a6b2f$1@newsgroups.borland.com>,
 "Dennis Jones" <nospam@nospam.com> wrote:

> Unfortunately, RAD Studio has its own build problems problems.  Try to 
> specify the output path for certain file types and you will discover that 
> you either can't specify them (HPP), or they won't go where you want (BPI).

> Build events can be used as a workaround, but it's a hack for a common bug

> in every C++Builder product since day one.  I wish they would concentrate 
> more effort in this area.

   Are these in QC?
-- 
David Dean (CodeGear)