Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Not 100% sure what you really want to achieve, but let me explain a few basics about WCF.</p> <p>A lot of programmers mistakenly take WCF to be some sort of a .NET remoting - e.g. they believe you're basically reaching out to a remote object on a server far away, calling a method on a "remoted" .NET object somewhere. This is absolutely not the case!</p> <p>WCF is about <strong>messaging</strong> - your client and server exchange nothing but <strong>serialized messages</strong> (and possibly headers) - but that's it. </p> <p>That said: those message exchange mechanisms are designed to be interoperable with a lot of non .NET platforms - Java, Ruby - you name it. They leverage the WSDL and XSD mechanisms to exchange descriptions of operations (WSDL) and the data structures being exchanged (XSD).</p> <p>WSDL and XSD are all about well defined, explicit calls and data structures. The functionality offered by those standards is the lowest common denominator between all SOA platforms - and as such, it's quite a bit more limited than what you might have grown accustomed to using pure .NET. The SOA world and the OOP world don't always match very well.</p> <p>So in the end, what you really need to understand and program against, are the standards as defined by WSDL/XSD - and as such, you need to forget about all .NET niceties like generics, interfaces and classes implementing those interfaces really quickly. They simply don't work over the WCF messaging infrastructure.</p> <p>All you can exchange between a WCF client and a WCF server is whatever you can describe and express in XML schema - concrete types made up of basic data types like strings, integers, and so forth. XSD supports a bit of inheritance, but it doesn't know squat about generics, and it doesn't deal with interfaces and non-concrete classes at all.</p> <p>So out of the box, I don't think your approach with a generic interface and messages implementing that interface and WCF figuring out what real method to call based on that class will fly. It's just not the way WCF was architected and designed to work. </p> <p>You might be able to create a custom (but concrete) base class, and you might be able to extend the WCF operation dispatcher on the server side to call different methods based on your classes being passed in (or some extra info in the headers coming along for the ride) - but I neither think that'll be easy, nor really the way WCF is intended to work - no guarantees that you'll really be able to pull it off.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to generically execute service operations in WCF?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmarc_s
    1. USmarc_s
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. COThanks for the well thought out answer Marc. I'm really just looking to extend the client proxies generated for me by Visual Studio (svcutil.exe) The Message contract classes that are code-generated for me are partial classes. This means that I can append purely client-side members to the client-side proxy classes to make them conform to a common interface. At that point, I'd like to write client-side functions to treat those messages the same since they have similar behavior -> paged results. I guess what I'm looking for is something client-side that can route a message based on it's type?
      singulars
      1. PO
      1. USCodeChef
    2. COOK, I understand what you're looking for, but I don't think WCF has anything to offer in that respect. You'd have to create your own layer on top of the client proxy with a generic interface, which would then call one of the several specific WCF client proxy methods, based on what type of message you're being passed in. Doable, but WCF doesn't offer any support here...
      singulars
      1. PO
      1. USmarc_s
    3. COYes, that's kinda what I'm finding out. The more that I looked at it, besides the MessageContract attribute, the code-generated message contracts offer little metadata to help route the message. I'll get my solution posted up here shortly for future readers.
      singulars
      1. PO
      1. USCodeChef
 

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