Sign in
Cyrus' Blather
Translate This Page
Translate this page
Powered by
Microsoft® Translator
Options
Blog Home
Email Blog Author
Share this
RSS for posts
Atom
RSS for comments
Search
Tags
No tags have been created or used yet.
Archive
Archives
November 2005
(1)
October 2005
(2)
September 2005
(11)
August 2005
(3)
July 2005
(5)
June 2005
(17)
May 2005
(8)
April 2005
(36)
March 2005
(30)
February 2005
(5)
January 2005
(7)
December 2004
(4)
November 2004
(5)
October 2004
(6)
September 2004
(16)
August 2004
(25)
July 2004
(35)
June 2004
(77)
May 2004
(73)
One step forward, Two steps forward
MSDN Blogs
>
Cyrus' Blather
>
One step forward, Two steps forward
One step forward, Two steps forward
Rate This
CyrusN
4 Jun 2005 3:33 AM
Comments
7
It was a great day today. Not just because i went to Mini-golf with my team and scored a 49 on a par 57 course, but because we finally completed our migration of the C# IDE source tree to the
MSBuild system
. We've wanted to do this for quite a long time but we never had the time to do a full migration and we also kept on running into a few issues that kept causing problems. So we worked with the MSBuild team to resolve all of them, and as of today we now build just fine with their fantastic system.
Plusses:
Clean build time reduced from 6 minutes 20 seconds to 2 minutes 40 seconds. That's 40% of the original build time!
The project file is incredibly clean. We have a simple wildcard inclusion will pulls in all *.h's and *.cpp's in our directory. This means we don't have to strugle with keeping a project file and our on disk files in sync. When we add a new cpp/h file anywhere in the directory (or subdirectory) MSBuild will pull it in
We only have one build system that we use now. We used to use the VS build system for command line builds (what eventually produces the final VS sku), and the VC++ build system for building within the IDE. We did this so we could code in the IDE and get things like IntelliSense and whatnot. This meant that we always had to keep two systems up to date. Nothing like trying to submit a checkin through our build system and realizing a few hours later that you didn't update the command line build system properly. Now we just have one project. The same project builds from the command line or inside the IDE *identically*
Much faster incremental rebuilds. Because MSBuild watches actual file accesses, it can do a much better job determing what to rebuild then our old build system. Faster incremental builds means quicker time between making changes and being able to use them.
Minuses:
Nothing
Great job MSBuild team! This is going to be a big boon for us!
7 Comments
Blog - Comment List MSDN TechNet
Comments
Loading...