DataSets, Web Services and Remoting

ahh that again

On the one hand you have Rocky Lhotka’s perfectly reasonable “NO”, on the other hand ADO.NET  not only encourages you to use and “abuse” webservices by enable the passing of DataSets from one end to the other, but with ADO.NET 2.0 we can pass DataTables too! And we will. Many many many of us will. Many more of us than the tiny percentage of .NET developers who do any interop. At the same time, ADO.NET 2.0 fixes the icchy dataset problem with remoting by making datasets now transmit as BINARY data, like the rest of the remoted objects. (I never had this problem because I have not coded ONE remoted application – ever. “My name is Julie and I’m a web service abuser“.)

Then of course is the whole new twist on this problem: teaching people how to use WSE with .NET clients and services. I do it all the time. I use it this way (because it is an easy way to implement security in the web services that I shouldn’t be using anyway) and these are the samples I use when I teach other people how to use WSE. And I’m not alone.

And to confuse us just a little more, here’s the latest  on .NET Remoting in .NET 2.0. Just remember: “no, nyet, niente, shake head vigorously.”

So here are the messages:

  1. Using web services in an end to end .net application is bad
  2. Use remoting for end to end .net applications
  3. Don’t put all your eggs into .NET remoting because, if though it’s not dead, in the future, you should be doing everything via services.
  4. Here’s how to do remoting in our closest future technology.

Maybe this isn’t the message that is supposed to be coming down to people like me, but that’s what it is sounds like by the time it does reach me. Am I consfused? Is Paris a city?

  Sign up for my newsletter so you don't miss my conference & Pluralsight course announcements!  

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.