XML as you noted is universal, but not performant. Binary for the win. (Binary remoting services in 2.0, TCP services [net.tcp among others] in WCF.)
Use WCF. Remoting is going away. Beyond that, check out some tutorials! :) ∞ Andy Badera ∞ +1 518-641-1280 ∞ This email is: [ ] bloggable [x] ask first [ ] private ∞ Google me: http://www.google.com/search?q=andrew%20badera On Wed, Oct 14, 2009 at 9:54 AM, B☼gus Excepti☼n <[email protected]> wrote: > > Datagrid <-> Win Form <-> Web Service Client <-> Web Service <-> SQL > Server 2005 > > I can't seem to find any documentation that describes how to put this > together. As my first example, all I want to do is update a DaataGrid > on a form and have the MSSQL DB on a remote machine update. Simple. > I'm looking for a binding solution that involves taking advanytage of > all things .NET. > > The talk of XML web services stresses compatibility with non.NET > clients, but I want _only_ .NET clients. How can I take advantage of > my .NET client this way? Whether to use WCF is treated elusively on > the MS site. When is it better? Worse? Can I even do what I need with > it? > > Is there a clear cut way to accomplish the above so that the binding > is transparent, and behaves just as if the datasource was on the same > machine as the client? > > TIA! > > :) >
