Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I use a contract-first approach, generally (but not always) using the same type representation at each end.</p> <p>Actually, to use WCF you don't need any special proxies etc; you can use your regular .NET types at both ends and not use <code>svcutil.exe</code> <em>at all</em>. Getting a working service is as simple as adding the "ABC" into the configuration file, and using something like:</p> <pre><code>public sealed class WcfClient&lt;T&gt; : System.ServiceModel.ClientBase&lt;T&gt; where T : class { public T Service { get { return base.Channel; } } } </code></pre> <p>Now you can use:</p> <pre><code>using(var client = new WcfClient&lt;IMyService&gt;()) { int i = client.Service.SomeMethod("abc"); } </code></pre> <p>and all you have at the client (and server) is your <code>IMyService</code> interface.</p> <hr> <p>For other tools; protobuf-net is an implementation of Google's "protocol buffers" API, which has a DSL for describing data and services in a "contract first" (and portable/interoperable) way - for example (a .proto file):</p> <pre><code>message SearchRequest { required string query = 1; optional int32 page_number = 2; optional int32 result_per_page = 3; } message SearchResponse { repeated string result = 1; } service SearchService { rpc Search (SearchRequest) returns (SearchResponse); } </code></pre> <p>The protobuf-net tool (which I maintain) includes a "protogen" utility to transform this DSL into C#/VB; and one of the options (for C#, at least - I'd need to check VB) is to emit a full WCF proxy implementation (with your choice of sync or async methods); very similar to svcutil - but (due to the protobuf-net relationship) it includes the custom <code>[ProtoBehavior]</code> attribute on the operation-contracts so that it uses the protobuf-net serializer instead of <code>DataContractSerializer</code> (faster and more efficient, but different).</p> <p>For VS integration; I'm working on exactly that (<a href="http://code.google.com/p/protobuf-net/source/browse/trunk/ProtoBufGenerator" rel="noreferrer">proof</a>).</p>
    singulars
    1. This table or related slice is empty.
    1. POContract-First SOA with WCF
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USMarc Gravell
    1. USMarc Gravell
    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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI actually explicitly need the ability to use different types at each end. One of the problems I am trying to solve is a build decouple. Right now, we have several domains that are dependent on each other, and they need to be more independent. Were looking to WCF to help us achieve that goal, as well as other core aspects of service-orientation. Our current architecture was designed from a very non-dotnet perspective (interestingly enough, it is primarily designed by java architects, not .net architects...you can imagine the disconnect.)
      singulars
      1. PO
      1. USjrista
    2. COProtocol buffers look interesting. You mentioned there is a C# generator. What about a WSDL generator? One of the things I am looking for is the ability to start with WSDL, and generate everything from that, DTO's and all, on both sides of the wire.
      singulars
      1. PO
      1. USjrista
    3. COprotobuf-net supports different types at each end as long as they meet the contract (for exmaple, I have it running with LINQ-to-SQL entities at the server and svcutil proxy entities on the client in one example). No WSDL for protobuf-net, as there is no need for a second language.
      singulars
      1. PO
      1. USMarc Gravell
 

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