VCBuild issues in MSBuild

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

Hence unless I use something like

>>vcbuild abc.sln /rebuild "Debug:Win32"

it wont work!!
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.

============================================================ ================
However any value like, Debug, "Debug|Win32" set as values to
VCBUILD_DEFAULT_CFG, gives error when VCBuild is run on the assembly.

Please help me.

Thanks & Regards

Uma

Re: VCBuild issues in MSBuild

"Uma Abhyankar" wrote in message
news:OEdcCFtWFHA.2128@TK2MSFTNGP15.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
>
> Hence unless I use something like
>
>>>vcbuild abc.sln /rebuild "Debug:Win32"
>
> it wont work!!
> 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.
>
> ============================================================ ================
> However any value like, Debug, "Debug|Win32" set as values to
> VCBUILD_DEFAULT_CFG, gives error when VCBuild is run on the assembly.
>
> 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.

VCBuild issues in MSBuild still present in Beta2 too!!

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" wrote in message
news:Oy5awjtWFHA.3620@TK2MSFTNGP09.phx.gbl...
>
> "Uma Abhyankar" wrote in message
> news:OEdcCFtWFHA.2128@TK2MSFTNGP15.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.
>