Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>There are 3 basic ways to create a WCF client:</p> <ol> <li><p>Let Visual Studio generate your proxy. This auto generates code that connects to the service by reading the WSDL. If the service changes for any reason you have to regenerate it. The big advantage of this is that it is easy to set up - VS has a wizard and it's all automatic. The disadvantage is that you're relying on VS to do all the hard work for you, and so you lose control.</p></li> <li><p>Use <code>ChannelFactory</code> with a known interface. This relies on you having local interfaces that describe the service (the service contract). The big advantage is that can manage change much more easily - you still have to recompile and fix changes, but now you're not regenerating code, you're referencing the new interfaces. Commonly this is used when you control both server and client as both can be much more easily mocked for unit testing. However the interfaces can be written for any service, even REST ones - take a look at <a href="http://vertigotwitter.codeplex.com/Wikipage" rel="nofollow noreferrer">this Twitter API</a>.</p></li> <li><p>Write your own proxy - this is fairly easy to do, especially for REST services, using the <code>HttpClient</code> or <code>WebClient</code>. This gives you the most fine grain control, but at the cost of lots of service API being in strings. For instance: <code>var content = new HttpClient().Get("http://yoursite.com/resource/id").Content;</code> - if the details of the API change you won't encounter an error until runtime.</p></li> </ol> <p>Personally I've never liked option 1 - relying on the auto generated code is messy and loses too much control. Plus it often creates serialisation issues - I end up with two identical classes (one in the server code, one auto generated) which can be tided up but is a pain.</p> <p>Option 2 should be perfect, but Channels are a little too limiting - for instance they <a href="https://stackoverflow.com/questions/2516914/getting-error-detail-from-wcf-rest">completely lose the content of HTTP errors</a>. That said having interfaces that describe the service is much easier to code with and maintain.</p>
    singulars
    1. This table or related slice is empty.
    1. POWCF ChannelFactory vs generating proxy
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USKeith
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWCF ChannelFactory vs generating proxy
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO@MurHaf Nope - this answer is entirely my own work. I ALWAYS attribute the contributions of others. I wrote this answer based on years of working with SOAP services in .Net at various jobs. That article that you link to is from March 2013, while my answer was written in April 2010 - 3 years before! If plagiarism has occurred he copied me. You should check dates before making accusations as it's very easy to do.
      singulars
      1. PO
      1. USKeith
    2. CO@MurHaf we don't even come to the same conclusions - that article recommends auto-generating a proxy (option 1) as 'simple'. I describe it as easy to set up, but messy and a pain to maintain. He doesn't even discuss writing your own proxy (option 3).
      singulars
      1. PO
      1. USKeith
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload