The importance of a clean build server was reinforced for me this morning. We’re getting ready to wrap up our first demonstration of our executable for users in a different timezone in London. Everything is wonderful on our developer workstations, but not so good on a clean box. It’s the normal culprit, a 3rd party control library needs some licensing info embedded into an assembly or has to be installed or something else. We found the problem easy enough before it hit the end users because we run the client on our build box that doesn’t have Visual Studio or the control libraries installed into the GAC. A clean build server finds these problems for you fast so the customer or testers don’t. Whatever you do, don’t put Visual Studio on your build box because it can fool you into thinking your installation script is complete when it only really works because of the assemblies that VS GAC’s for you.
How I'm using StoryTeller to test FubuMVC
Building a "Lookup" html convention w/ FubuMVC
FubuMVC's Configuration Model "Special Sauce"
Managing Script dependencies with FubuMVC
Authorization and FubuMVC
Composing Views with FubuMVC
Extensible Model Binding with FubuMVC
Modular Packaging with FubuMVC
Self-Installing Apps w/ FubuMVC
Routing and Behavioral Conventions with FubuMVC
What Should I Learn?