I have seen numerous blog and newsgroup posts about how XmlSerialization and ASMX WebServices serialize DateTime in v1.0 and v1.1 of the framework. Well, I have some good news, bad news and good bad news for you. Good news: We fixed it. Bad news...

This is a long post so I’ll summarize my findings up front. Summary: Following the .NET Remoting guidance enables quick and painless upgrade to WCF A single interface can be decorated to support .NET Remoting, WCF and ASMX The service...

Here is the final trick. And those of you who have read the series have waited a while for this final post. (Sorry for the delay.) Programming against an interface gives you the consistent programming model across the various distributed platforms but...

A little self-promotion never hurt anyone... Some new MSDN TV content has recently been made available on the new features of .NET Remoting for .NET Framework 2.0. Enjoy! http://msdn.microsoft.com/msdntv/episode.aspx?xml=episodes/en/20050120NETMT...

Now that you expose the your remote object through a CLR interface, that interface should limit itself to interfaces and serializable types as parameters and return values. This guideline is really just an additional follow-on to rule one about using...

In Part 1 it was suggested to use only interfaces to program against your remoted object. Another consideration for enforcing the correct usage of your remote object is to limit access to the implementation except through the interface that you defined...

One of the easiest ways to avoid locking yourself into .NET Remoting is to avoid exposing its most infamous type in your contract: MarshalByRefObject (MBRO). To marshal object references in .NET Remoting your type needs to inherit from MBRO but that doesn...

So you've heard about SOA and Indigo and the future of distributed application development on .NET. You've even seen the long-running discussion of our guidance on Richard Turner's blog. You are now asking yourself: But how can I use .NET Remoting...

Now that I have your attention... We are seriously considering deprecating the SoapFormatter in .NET Framework 2.0. It is the nexus of a whole host of serialization issues and implies a promise of interop that it does not and will not live up to. It...

I'll be going to TechEd Europe to give a few talks. If you are interested in any of the following then add them to your schedule: Wed 8:30 CTS201 Web Service, XML Serialization and Networking in .NET Framework 2.0 A preview of some of the...

Interested in Web Services features in Whidbey? So am I! Yasser Shohoud, Software Legend, and I will be giving a talk at TechEd to introduce some our favorite new Web Services features to you at TechEd. The new talk (CTS201) is not even in the Session...

Those of you scouring the list of talks at TechEd for in-depth .NET Remoting discussions will be disappointed. .NET Remoting will be touched on in the Connected Systems track (CTS300) by Richard Turner but that will be prescriptive guidance for the usage...

As a first blog entry, I figure introductions are in order. I am Matt Tavis, PM at Microsoft working on the .NET Framework 2.0 (Whidbey) and Indigo. My Whidbey features areas are .NET Remoting, runtime serialization and xml serialization.