Plan for success: advice and architecture during the design phase.
Expert Sitecore development and implementation.
Continuous improvements and site maintenance.
Continuous integration, site monitoring, and trouble-free deployments.
Assess an existing implementation to find the top opportunities for improvement.
Get Sitecore's latest and greatest marketing powers.
Ensure an error-free site before—and after—launch.
Easily move content, templates, workflows, and more to Sitecore.
Create experience-focused commerce with Sitecore.
Maximize Sitecore's advanced market capabilities.
Please reach out with any questions or to schedule a free consultation Contact Us
Digital marketing technology, strategic insights, & technical advice.
Best Practices, tips, and advice for digital marketers & technologists.
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.
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.
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).
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...