Building .NET projects: NANT vs. MSBuild
Nov 09, 2011
So for .NET projects, we should be using NAnt and/or msbuild or a combination of them. Cesar Intriago will write something more comprehensive on this at a later date, but here are some links to discussions on the tradeoffs of each.
The general consensus here is that no one except the Microsoft employees that work on their <build/> team like msbuild, but there are certain things that can ONLY be done in MSBuild.
The most obvious thing I've seen is that NAnt's <csc> task can't compile classes that where the imports are predefined for the project (i.e. allowing developers to be lazy and not have to have "using Scripps.Website..." statements at the top of all their classes).
Maybe I need to be more progressive about the need for importing packages/namespaces. I suppose with Intellisense (as long as you are viewing the class within your IDE), you don't need the import/using statements at the top to let you know where classes are located. And with the advent of the IDE dropping the import/using statement automatically for you, maybe importing packages/namespaces will become a thing of the past...
Frequently Asked Questions
XM Cloud is a fully-managed self-service platform that allows developers and marketers to efficiently launch engaging omnichannel experiences in the cloud. All of this is achieved using Sitecore’s headless architecture.
Sitecore Azure gives enterprises an interface to manage their cloud delivery infrastructure and simplify deployment to Microsoft Azure.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.