Any Change in .NET 4.0 in How to PROPERLY call a WCF Service?

Question

I am asking for some advice (so sorry if this has been asked before):

When I call WCF services I use the following pattern. I developed this pattern way back with early WCF releases (in VS2008) and am curious now if this Close()/Abort() pattern is still necessary in the current version of WCF (in VS2010). It certainly does work.

I have looked into this and I see many examples calling WCF clients without this pattern, but I also know that many samples on the Internet are inferior. But is it overkill? What's the ideal pattern?

If you do have the answer, it is very important to me that you provide some type of reference so I can research into your suggestion.

  var _Client = new MyServiceReference.MyServiceClient();
  try
  {
      var _Item = _Client.GetItem(123);
      _Client.Close();
      return _Item;
  }
  catch
  {
      _Client.Abort();
      throw;
  }

although I'm curious why you choose a non MSFT variable name convention — Sebastian, Mar 08 '12 at 12:11
@SebastianGodelet agree to disagree: http://stackoverflow.com/a/6459604/265706 Pretty strandard! — Jerry Nixon, May 20 '12 at 04:21

marc_s · Accepted Answer · 2011-03-09T20:15:47.927

5

Yes, this is still pretty much the recommended best practice.

See: MSDN Avoiding Problems with the Using Statement

Not much has changed in the way the WCF clients call a service, and how to deal with exceptions and errors.

edited Mar 09 '11 at 20:15

answered Mar 09 '11 at 19:40

marc_s

732,580
175
1,330
1,459

Do you know where this best practices is recommended by MSFT? – Jerry Nixon Mar 09 '11 at 19:57

score 0 · Answer 2 · edited Jun 12 '13 at 09:34

0

For consume the WCF Service with avoiding Using approach, I found this wish that help you.

edited Jun 12 '13 at 09:34

Dilip Manek

9,095
5
44
56

answered Jun 12 '13 at 09:16

Savangchai Saroj

23
4

Any Change in .NET 4.0 in How to PROPERLY call a WCF Service?

2 Answers2

Linked