public WidgetScheduleCollection GetScheduledWidgets(WidgetRequest para)
        {
            WidgetRequest1 request;
            WidgetResponse response;

            string defaultEndPoint = ConfigurationManager.AppSettings["DefaultEndPoint"].ToString();

            BasicHttpBinding binding = new BasicHttpBinding();
            EndpointAddress endPoint = new EndpointAddress(defaultEndPoint);

            // Use Channel so we don't have to rely on config file
            ChannelFactory<WidgetServiceContract> channelFactory =
                new ChannelFactory<WidgetServiceContract>(binding, endPoint);

            WidgetServiceContract service = channelFactory.CreateChannel();
            using (service as IDisposable)
            {
                // Wrap the request with a Channel's WidgetRequest
                request = new WidgetRequest1(para);

                // Get the scheduled Widgets for request
                response = service.GetScheduledWidgets(request);
            }

            // Return the Widget collection
            return response.ScheduledWidgetCollection;
        }

 

pbolduc wrote:
This article was very interesting to read regarding using WCF and IDisposable etc.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=855018&SiteID=1

and a couple of MSDN links:

Avoiding Problems with the Using Statement

Expected Exceptions

Thanks for taking the time to provide these references!   This topic wasn't given much emphasis in the WSSF....   After reading your links I revisited the WSSF factory forum and found that SpencerClark (Apr 4) provides wrapper code which implements the code recommended in the links - he indicates that he has "not had a single error where the service was faulted".    Looks like I have a wee bit of refactoring to do on Monday ;)