Since there is so much interest in this msbuild thing, here's the list of namespaces Microsoft.Build.BuildEngine
When you open the link, click on 'sync toc' to see the rest of Microsoft.Build.* namespaces in the TOC. http://longhorn.msdn.microsoft.com/?//longhorn.msdn.microsoft.com/lhsdk/ref/ microsoft.build.buildengine.aspx d. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brant Carter Sent: 28. listopad 2003 23:40 To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [nant-dev] FYI I am at PDC and attended the session last night. The MSBuild is basically NAnt with the following differences. [1] Now the Visual Studio project file is the "build" file. This allows for much tighter integration between VS and the build tool. In fact VS now "shells" out to the build tool directly. [2] The syntax is slightly different for using tasks. Instead of using <taskname> as the tag you use the <task name="taskname">. [3] The tag names are all MixedCase instead of NAnts lowercase. [4] They renamed some of the concepts like filesets etc.. [5] There is a need feature where you can create output sets. These are like filesets but are used as the output of a task. You use the @() syntax [6] Property syntax is $() instead of ${} The big bad news is that they haven't really improved anything, just changed it. It would have been nice to see some sort of .sln support and a tool for generating build-order dependencies from a set of assemblies. Also note that this won't be supported/usable until Whidbey or late 2004 so anyone doing development now is stuck. cheers brant ... >From: "Jaroslaw Kowalski" <[EMAIL PROTECTED]> >To: "Tom Cabanski" ><[EMAIL PROTECTED]>,<[EMAIL PROTECTED]>,<nant-users@ >lists.sourceforge.net> >Subject: Re: [nant-dev] FYI >Date: Tue, 28 Oct 2003 20:47:46 +0100 > >Sounds like they've invented ant ;-) For some interesting comments, see: > >http://blogs.gotdotnet.com/korbyp/commentview.aspx/c6c8775e-74b3-4d9c-9 >71b-615f744cc1e5 > >Do you think that NAnt should be changed to support MSBuild's XML >format in the future? >Or even abandon current format to promote compatibility? > >(I know that without the knowledge of the format you cannot tell, but I >think it will be very similar to ant/nant, so that the conversion >should be pretty easy) > >Jarek > >----- Original Message ----- >From: "Tom Cabanski" <[EMAIL PROTECTED]> >To: <[EMAIL PROTECTED]> >Sent: Tuesday, October 28, 2003 8:14 PM >Subject: [nant-dev] FYI > > > > I think I would still prefer NAnt because it is cross-platform and >open-source, but found this little blurb interesting. I wonder if it >is in the preview stuff being passed out at the PDC this week? I guess >I'll have to order up my copy and see (I get it as part of my companies >solution provider subscription). > > > > For those that do not know, Whidbey is the project name for the next >version of VS.NET. Up to now, I've been most interested in the new C# >features -- most notably, generics. > > > > >> MICROSOFT BLURB FOLLOWS << > > Product Build > > > > Historically, developers have struggled when trying to map a > > complicated >build infrastructure into the Visual Studio IDE. Roadblocks >traditionally center around the inability to fully customize or >understand what happens when a project is built within the development >environment; the failure to reproduce a build within a build lab >environment where Visual Studio is not likely to be present; and the >limitations of a build system that was not optimized to model entire products, but rather single projects. > > > > The Whidbey release of Visual Studio will radically improve this > > area of >software development by introducing a new build engine called MSBuild. >Key design goals for MSBuild include: delivering a file format that is >well-documented and backed up by a published XML schema definition; >making the MSBuild engine an integral part of the .NET Framework >redistributable; allowing developers to customize, augment or >completely redefine the build process; and providing seamless >integration with the Visual Studio Whidbey IDE. > > > > First, MSBuild will introduce a new XML-based file format that is > > simple >to understand and easy to extend. The MSBuild file format will enable >developers to fully describe what artifacts need to be built, as well >as how they need to be built under different configurations. In >addition, the file format will enable developers to author reusable >rules which can be factored into separate files so that builds can be >done consistently across different projects within a product. > > > > Second, MSBuild will ship as a core part of the Whidbey .NET > > Framework >redistributable. This shift in philosophy will allow developers to rely >on the MSBuild infrastructure regardless of IDE presence and licensing issues. >In addition, by providing MSBuild class libraries as a core part of the >.NET Framework, developers will be able to create and debug components >of a customized MSBuild process using the managed language of their >choice. > > > > Third, MSBuild will be completely transparent with regards to how it >processes and builds software. All build steps will be explicitly >expressed in the XML project file regardless of whether it was authored >by hand or auto-generated by the Visual Studio Whidbey IDE. This also >means that Visual Studio no longer treats any part of the "F5" build >experience as a black box. A user can now understand, replicate, edit, >remove, or augment any part of the build process. > > > > Finally like its predecessors, MSBuild will be fully integrated into > > the >Visual Studio Whidbey IDE. This tight integration will enable >developers to take advantage of all the built-in productivity features >Visual Studio offers, while allowing developers to scale, customize, >and adapt the Whidbey build system to their unique infrastructure >needs. > > > > > > ------------------------------------- > > TFC > > > > > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: SF.net Giveback Program. > > Does SourceForge.net help you be more productive? Does it > > help you create better code? SHARE THE LOVE, and help us help > > YOU! Click Here: http://sourceforge.net/donate/ > > _______________________________________________ > > nant-developers mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/nant-developers > > > > > >------------------------------------------------------- >This SF.net email is sponsored by: SF.net Giveback Program. >Does SourceForge.net help you be more productive? Does it >help you create better code? SHARE THE LOVE, and help us help >YOU! Click Here: http://sourceforge.net/donate/ >_______________________________________________ >nant-developers mailing list >[EMAIL PROTECTED] >https://lists.sourceforge.net/lists/listinfo/nant-developers _________________________________________________________________ Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
