Saturday, September 07, 2002

.NET Remoting or ASP.NET Web Services. MSDN has two exciting new articles on an area that is of confusion to many (myself included): when do you use .NET Remoting and when do use ASP.NET Web Services. Its interesting how they are listed with order reversed in other case. The first is ASP.NET Web Services or .NET Remoting: How to Choose and the other is Performance Comparison: .NET Remoting vs. ASP.NET Web Services. [Sam Gentile's Radio Weblog] 8:58:14 PM     Don't use DataSets if you want Interop and YES you do want Interop!. Of course. Gordon is 1000% correct in noting that .NET DataSets will not interoperate with any other toolkit and questioning the author's motives. As Tim said in the other articles I listed "Consumers of this WSDL definition are meant to understand the special significance of this "well-known" URI—it is the four-part strong name of a specific runtime assembly included in the .NET Framework. This style of WSDL is great for clients that are implemented using .NET Remoting because they can generate a proxy assembly with the right information for marshaling. However, for other Web service toolkits—including ASP.NET—that do not understand this URI and expect to find a schema definition for the DataSet type, this WSDL will be useless." I wanted to list the article for completeness next to the better MSDN articles for  those in a limited Intranet Microsoft type of solution who may want to do this internally. But yes, its really bad for Interop! [Sam Gentile's Radio Weblog] 8:56:32 PM

© Copyright 2004 Thomas Wagner. Last update: 5/2/2004; 4:44:52 PM. This theme is based on the SoundWaves (blue) Manila theme.