I want to use msbuild to build my project files on a build lab machine that does not have VS installed.
I have make some test with Visual Basic and C# project without any problem.
but with c++ it 'seems to be, a little more difficult.
Msbuild refused the Release option configuration :
If i use
msbuild myproject.vcproj /t:Rebuild
that build both Release and Debug version of my project
I want only release version, so I try
msbuild myproject.vcproj /property:Configuration=Debug /t:Rebuild.
with the same result.
Reading info on the Net it seems that Msbuild doesn't work correctly whith c++ project
Where is the truth
Is the use of MSbuild with c++ project fully supported
Best Regard
msbuild for all Visual Studio Projects
Hot Topic
- MSDN 2005 not integrated with visual studio 6.0
- msbuild publish not copying application1.exe.config.deploy
- Cell.Range catches more than it's supposed to?
- i have the some problem on win 2000 platform
- report designer can't access referenced datasets
- Many Package Load Failures with Beta2
- Namespace URI URN - what shall I use?
- ParameterFieldCurrentValueException when exporting or printing crystal report
- Object reference not set to an instance of an object
- VB6/VSS Questions
Visual Studio
- VS2005 on XP 64 bit Itanium
- SQL connection string
- Expression Interactive Designer March CTP crashing
- Unable to debug: The binding handle is invalid
- What about LINQ somehow running inside of Excel
- What's the soure of this 3D rendering "bug"?
- ContinueOnError, yet still failing the build?
- Bind to property outside DataContext
- Cant create new Project or Open Project
- {x:Static ...} treated as a string when used in certain properties
msbuild for all Visual Studio Projects
CHASE10541
The state of things for Whidbey is that unfortunately VC projects are not in the MSBuild format and MSBuild doesn't support building them natively. However, we will ship with a set of tasks and engine side support for building VC projects by invoking VCBuild.exe (you'll need to install .NET SDK to get it).
As you have seen yourself, in Beta2 the level of support for VC projects is very limited. We're working to improve it for RTM - the plan is that you should be able to build VS solutions containing VC projects and/or VC projects individually, but the exact level of support for project-to-project references still remains to be seen. We are aware that this is not an optimal solution and if we can't get it 100% right for Whidbey, we will investigate possible ways to improve the experience before the next big release.
I'm sorry I can't offer you a better answer. It would help if you shared with us what kind of solutions you intend to develop/build - what kind of projects (C#, managed C++, native C++) and what kind of dependencies/references between them. Just the big picture, the more real world data we have the better. If you don't feel like describing this on a public forum, feel free to send us mail at MSBuild@microsoft.com.
thanks,
Lukasz