VCBuild issues in MSBuild still present in Beta2 too!!

[Uma Abhyankar]

Hello All,
I was facing an issue with VCBuild on Beta1. Today after shifting to .NET
Beta2, it looks like the issue is still not resolved :-(

I have to invoke VCBuild through MSBuild on command prompt. I have
following issue:

Issue:
--------
MSBuild can invoke VCBuild internally. However it invokes VCBuild without
passing any config options. Only the target, Rebuild or clean options are
passed. The Debug or Release options are not, hence always both
configurations are built for any assembly.
For instance a command like:

prompt> msbuild abc.sln /t:rebuild /p:config=debug
will internally invoke
prompt> vcbuild abc.sln /rebuild

would build both release and Debug. We do not want that!!

Note: We do not have any project to project references in the vcproj. Also
we want to use MSBuild for building all our projects...

Could someone help...Please.. .

Regards
Uma

"Peter van der Goes" <p_**********@t oadstool.u> wrote in message
news:Oy******** ******@TK2MSFTN GP09.phx.gbl...

"Uma Abhyankar" <au**@persisten t.co.in> wrote in message
news:OE******** ******@TK2MSFTN GP15.phx.gbl...

Hello,

I am using .NET Beta1 Visual Studio.

I have to invoke VCBuild through MSBuild on command prompt. I have
following
issues:

Issue1:
--------
MSBuild invokes VCBuild internally. However it invokes VCBuild without
passing any config options. Only the target, Rebuild or clean options are
passed. The Debug or Release options are not, hence always both
configurations are built for any assembly.
For instance a command like:

msbuild abc.sln /t:rebuild /p:config=debug

will internally invoke

vcbuild abc.sln /rebuild

would build both release and Debug. We do not want that!!
Issue2:
--------
There is a note written in VCBuild /help as follows:
Default Behavior:

=============== =============== =============== =============== =============== =
==

If no project is specified, and there is only a single .vcproj file in
the

directory, that project will be built.

If no configuration is specified, and the VCBUILD_DEFAULT _CFG environment

variable is set, the configuration it specifies will be built. If it is
not

set, then all configurations will be built.

The default action is to build the specified configurations without
cleaning.
Options will also be read from the VCBUILD_DEFAULT _OPTIONS environment
variable.

=============== =============== =============== =============== =============== =
Even this does not work, when msbuild invokes Please help me.

Thanks & Regards

Uma

If you are referring to Visual Studio 2005, you're using an obsolete beta.
I'd suggest the you download Beta 2, then see if your issues have been
addressed.

http://lab.msdn.microsoft.com/vs2005/

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.

[Craig Lichtenstein]

After seeing some vcbuild issues online, I've been prototyping a tool that
could convert vcproj files to msbuild files.
Additionally, I've begun creating cl and link msbuild tasks so vcbuild
wouldn't be necessary for simple circumstances.
I'm currently trying to assess how interested people would be in such a
tool. If you are interested, please let me know.
--
DDCPX - Helping Developer Division create positive customer experiences
throughout the product life cycle.
http://blogs.msdn.com/clichten

"Uma Abhyankar" wrote:

Hello All,
I was facing an issue with VCBuild on Beta1. Today after shifting to .NET
Beta2, it looks like the issue is still not resolved :-(

I have to invoke VCBuild through MSBuild on command prompt. I have
following issue:

Issue:
--------
MSBuild can invoke VCBuild internally. However it invokes VCBuild without
passing any config options. Only the target, Rebuild or clean options are
passed. The Debug or Release options are not, hence always both
configurations are built for any assembly.
For instance a command like:

prompt> msbuild abc.sln /t:rebuild /p:config=debug
will internally invoke
prompt> vcbuild abc.sln /rebuild

would build both release and Debug. We do not want that!!

Note: We do not have any project to project references in the vcproj. Also
we want to use MSBuild for building all our projects...

Could someone help...Please.. .

Regards
Uma

"Peter van der Goes" <p_**********@t oadstool.u> wrote in message
news:Oy******** ******@TK2MSFTN GP09.phx.gbl...

"Uma Abhyankar" <au**@persisten t.co.in> wrote in message
news:OE******** ******@TK2MSFTN GP15.phx.gbl...

Hello,

I am using .NET Beta1 Visual Studio.

I have to invoke VCBuild through MSBuild on command prompt. I have
following
issues:

Issue1:
--------
MSBuild invokes VCBuild internally. However it invokes VCBuild without
passing any config options. Only the target, Rebuild or clean options are
passed. The Debug or Release options are not, hence always both
configurations are built for any assembly.
For instance a command like:

> msbuild abc.sln /t:rebuild /p:config=debug
will internally invoke
> vcbuild abc.sln /rebuild

would build both release and Debug. We do not want that!!
Issue2:
--------
There is a note written in VCBuild /help as follows:
Default Behavior:

=============== =============== =============== =============== =============== =
==

If no project is specified, and there is only a single .vcproj file in
the

directory, that project will be built.

If no configuration is specified, and the VCBUILD_DEFAULT _CFG environment

variable is set, the configuration it specifies will be built. If it is
not

set, then all configurations will be built.

The default action is to build the specified configurations without
cleaning.
Options will also be read from the VCBUILD_DEFAULT _OPTIONS environment
variable.

=============== =============== =============== =============== =============== =
Even this does not work, when msbuild invokes Please help me.

Thanks & Regards

Uma

If you are referring to Visual Studio 2005, you're using an obsolete beta.
I'd suggest the you download Beta 2, then see if your issues have been
addressed.

http://lab.msdn.microsoft.com/vs2005/

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.