Build --> Publish. Done.
Validation: http://weblogs.asp.net/scottgu/archive/2010/01/15/asp-net-mv...
These features are designed so that the validation logic is always enforced on the server, and can optionally also be enforced on the client via JavaScript. The validation infrastructure and features in ASP.NET MVC 2 are designed so that: 1) Developers can easily take advantage of the DataAnnotation validation support built-into the .NET Framework. DataAnnotations provide a really easy way to declaratively add validation rules to objects and properties with minimal code.
2) Developers can optionally integrate either their own validation engine, or take advantage of existing validation frameworks like Castle Validator or the EntLib Validation Library. ASP.NET MVC 2’s validation features are designed to make it easy to plug-in any type of validation architecture – while still taking advantage of the new ASP.NET MVC 2 validation infrastructure (including client-side validation, model binding validation, etc).
2) To use it you have to use strongly-typed views, and HTML helpers I believe.. which again I don't care for since it is taking the markup out of your hands.
With respect to #2, I strongly suggest you reevaluate. Strongly-typed views will save you a lot of boilerplate code in your controllers and HTML helpers only interfere with your markup to the extent you want them to. Most of them are super minimal and easily styled or manipulated. I expected that the helpers would just be different ways of getting into the same mess you encounter using things like server controls in webforms but I was quickly shown otherwise.
Also, testing. Try testing in C# vs. Ruby or any other dynamic language.
I don't know anyone who uses the built in Form Validation, you would only use that if you don't care about your client-side code.. for people who care we still end up doing both by hand.