MVC 2 Presentation at DC DNUG

Wednesday night (8/25/2010) I will be presenting Top 10 Ways MVC 2 Will Boost Your Productivity [http://www.dcdnug.org/dnn/Meetings/tabid/61/ModuleID/399/ItemID/3/mctl/EventDetails/Default.aspx] at DC DNUG [http://www.dcdnug.org/dnn/Home.aspx]. This is a brand new user group that just started a couple of months ago and it will be my first time there. I hope to see you there!...


RESTful WCF Services with No svc file and No config

While Microsoft continues to add features to WCF with each version, they are also adding features that simplify working with WCF services as well. Historically WCF has been somewhat intimidating to the uninitiated because of the non-trivial configuration for endpoints including behaviors, bindings, and much more. For this reason, a lot of people stayed with "old school" asmx web services. With the new features of WCF 4, you can build powerful web services with no svc file and no endpoint configu...


Generics, Reference Types, Value Types, and Interview Questions

Generics are nothing new and have been part of .NET for over 5 years. Reference types and value types are core concepts in the CLR type system and these concepts have been the same since .NET was released – they are also nothing new. However, when I ask about these concepts during interviews, I often get a wide range in quality of the answers to these questions. If you get asked about these topics in an interview, be prepared to give great answers! You don't have to give a textbook perfect memor...


Validating a Dynamic UI with MVC 2

When MVC 2 was released, there was a last minute change to use Model Validation instead of Input Validation [http://bradwilson.typepad.com/blog/2010/01/input-validation-vs-model-validation-in-aspnet-mvc.html] . Essentially, Model validation means that your entire view model will be validated regardless of which values actually got posted to the server. On the other hand, with Input validation, only the values that get posted to the server will get validated. While this was the right decision by...


AppFabric Workflow Persistence Not Fully Functional Because Net.Pipe Protocol is Missing

When setting up my AppFabric environment yesterday, I was running into (what I thought) was a strange error: > Workflow persistence is not fully functional because the net.pipe protocol is missing from the application's list of enabled protocols. At first, I was quite confused by this. I had double-checked to make sure that net.pipe was enabled.  First I checked the Site Bindings for the web site itself: Next, I check the Enabled protocols by going to "Advanced Settings" at the appli...