printf(“Hello MSBuild!\n”);

Bogdan Mihalcea: The New VC++ Project/Build system - MSBuild for C++

ComponentGear.com Feed — Thu, 18 Jun 2009 21:54:04 GMT

Bogdan Mihalcea is a developer on the VC++ build and project system team. He and team have been very

Visual Studio 2010 New Features, Extensibility Points and Partner Opportunities

Visual Studio, VSIP Partners and more ...... — Wed, 20 May 2009 01:52:00 GMT

As part of my role in working with partners in the Visual Studio Industry Partner (VSIP) Program I have

VC MSBuild Extensibility Example

Visual C++ Team Blog — Thu, 02 Apr 2009 01:02:16 GMT

Hello, my name is Felix Huang and I am a developer on the Visual C++ team. Over the last year, I worked

MSBuild Task

Visual C++ Team Blog — Tue, 16 Dec 2008 20:12:27 GMT

Hello again! My name is Li Shao. I am a Software Design Engineer in Test in the Visual C++ group. As

Project filters

Martin Filteau — Mon, 08 Dec 2008 17:45:55 GMT

I'm wondering why the filters are in a separate *.vcxproj.filters file.

Wouldn't it be easier to keep this information in the *.vcxproj itself under the <ProjectExtension> node?

.vsprops

Jean-Marc — Sat, 06 Dec 2008 13:31:28 GMT

Since we found this feature in VS2005, project-setttings-hell has been a bad memory from the old days. Comes in handy if you have a multi-million C++ code base with hundreds of .vcproj files. So in our opinion, MSBuild should support the .vsprops.

re: printf(“Hello MSBuild!\n”);

jon — Fri, 05 Dec 2008 16:21:29 GMT

"I'll let the owner of the property pages dialogs speak to the feedback about them directly."

I'm not noticing a whole lot of feedback from this person as yet :)

re: printf(“Hello MSBuild!\n”);

Aaron — Thu, 27 Nov 2008 01:17:53 GMT

since it supports native multi-targeting can you add support for the Visual C++ 1.52 compiler so we can compile our 16-bit applications without having to be on a Windows NT machine?

re: printf(“Hello MSBuild!\n”);

David — Mon, 24 Nov 2008 22:04:06 GMT

@Leo:

> I lost count of the number of times I have found inconsistent settings between builds as a result of this GUI and whenever I have to make changes or create a new project I end up swearing at it.

I have found that Property Sheets (.vsprops files) are a great help when the number of projects, platforms and configurations increase. Instead of specifying lots of settings on the project level, I try to refactor the settings into a few .vsprops files (e.g. Debug.vsprops, Release.vsprops, X86.vsprops, X64.vsprops) and leave the .vcproj files to all defaults, inheriting everything from the property sheets. That's it, not a single entry in bold in the project properties (or at least very few). It takes some time initially to find the optimal structure, but once you have organized all settings into a few .vsprops files, you are less likely to end up with the inconsistencies that you describe.

I hope that VS2010 keeps improving on this feature, because I find it invaluable for big multi-project solutions. For example, source control integration is not great for .vsprops files in VS2008.

re: printf(“Hello MSBuild!\n”);

Dan — Mon, 24 Nov 2008 21:49:26 GMT

I'll let the owner of the property pages dialogs speak to the feedback about them directly.

However, as the MSBuild owner, I can say that moving to MSBuild means that the file format is fully documented and supported, that Visual Studio is expected to handle whatever structure you create and whatever content you put in there, and that there will be a comprehensive, rich new object model over it.

(This will replace the object model MSBuild currently has, which has many deficiencies.)

So regardless of what the dialog supports in VS10, there will be plenty of opportunities to write powerful custom tools over the project files and property sheets to display in any format and allow any kind of editing: perhaps 3rd parties will create some.

Dan