This isn't a new topic by far, but I still encounter the question of how to implement a read-only auto-implemented property, so here it goes. 

As I'm sure you are aware, C# 3.0 has a wonderful feature known as auto-implemented properties (sometimes referred to as Automatic Properties).  These clean up our code quite a bit when we have properties that are simply backed by a private member, and all we do it get and set that value. More...

If you are working with a WCF service, an MSMQ binding, and hosting in IIS, there are three wonderful articles by Tom Hollander that you should check out.  The series is entitled "MSMQ, WCF and IIS: Getting them to play nice", here are the three links:

• MSMQ, WCF and IIS: Getting them to play nice (Part 1)
• MSMQ, WCF and IIS: Getting them to play nice (Part 2)
• MSMQ, WCF and IIS: Getting them to play nice (Part 3)

They sure have helped me get one of my projects working, and I'm sure they will help you as well.

It's been entirely too long since my last post, and with the olympics in full swing, we'll go with a volleyball theme for this post.

BUMP

So here's the scenario. After really digging your teeth into ASP.NET 2.0 and playing around wiih all the cool data access features, you decide to apply a liberal use of the ObjectDataSource for its ability to take care of the paging and sorting calls for you. Now, you begin to convert your site to a service oriented back end and you wonder how you're going to make calls against your web service. You have a few options in front of you. You can create a thin facade layer that will act as a liaison between your presentation code and your service layer calls, and hook your ObjectDataSource to that. This works especially well when you have a complex object model that makes use of the web service calls behind the scenes. It's also beneficial when you are generating your proxy classes from metadata or contacting a foreign web service. In the scenario I'm going to demonstrate here, I'm referencing a shared contract and service library, so I'll be using using the ObjectDataSource to make direct calls to ChannelFactory<T> for this example.

More...