Thursday, September 12, 2002

Intel Rich Client Series. I'd like to announce a new series of articles specially requested by Intel on the topic of making the most of the client tier. Topics include high-performance graphics, data and XML querying and filtering on the client-side, smart client deployment and more. Two articles are up now with more to come through the end of the year. Enjoy. [sellsbrothers.com: Windows Developer News] 10:46:08 AM

Rich Client Database Interactions with ADO.NET. Shawn Wildermuth and Chris Sells "In the .NET Framework, rich clients can bring database servers to their knees, just like Web-based applications. But with the disconnected nature of ADO.NET, your rich clients can manipulate and analyze database data without impacting the database server. Once you have the data in the rich client, you can do high-performance analysis of the data—including sorting, filtering, and querying—without expensive server calls. In this article we will show you how to use DataSet, DataView, and XmlDataDocument to make your rich clients work with database data in a disconnected way." [sellsbrothers.com: Windows Developer News] 10:45:52 AM

Multithreaded .NET Web Service Clients. Ian Griffiths and Chris Sells "Unresponsive programs are extremely frustrating to use. Applications that sometimes freeze for a moment are a source of much irritation, especially if they don't provide any feedback on what they are doing, or how long it is likely to be before they start responding again. This behaviour can be particularly common among applications that use remote facilities such as Web services. This article describes how to maintain responsiveness in .NET Windows Forms rich client applications, even when invoking potentially long-running Web services, by using multiple threads." [sellsbrothers.com: Windows Developer News] 10:45:26 AM

foreach is Your Friend: Part 2. Just when you'd thought you're learned everything there was to know about foreach in part 1, I've got more in part 2! This part (the final : ) discusses implementing support for foreach in your own custom types as well as how to patch holes in the framework where they forgot to add foreach support. Enjoy. [sellsbrothers.com: Windows Developer News] Is Chris on a roll today? 10:45:00 AM

Less Than 40 Seats Left at the Web Services DevCon. Register now for the Web Services DevCon, October 10-11 in greater Boston, featuring Don Box, Tim Ewald and keynote speaker Sam Ruby. In addition to amazing talks by Microsoft’s Web Services Program Manager, Keith Ballinger, and IBM Distinguished Engineer, Noah Mendelsohn, as well as wizened practitioners from HP, Macromedia and the W3C, all attendees receive exclusive SellsBrothers t-shirts available nowhere else. Register now! [sellsbrothers.com: Windows Developer News] 10:44:12 AM

Jim Allchin wants more consumer oriented Web Services. "When we look out on the landscape, we don't see enough Web sites--and, in particular, customer-facing sites--that have XML Web services interfaces that people can take advantage of," Jim Allchin, Microsoft's senior vice president for Windows, told CNET News.com [via CNET News.com] [Paresh Suthar's Radio Weblog] Maybe if they implemented all of GXA (specs does not equal robust proven implementations) and had it out there in full, we would. Right now, there isn't enough of a robust infrastructure and services for consumer oriented Web Services. 5:37:12 AM

Thanks to Clemens Vasters for clearing up a place of confusion for me on whether COM/Interop marshaling happens for COM+  components in the EnterpriseServices namespace of .NET or ServicedComponents.  It doesn't. This would have been rather inefficient if it did. He says "Replicating a post to the DM dotnet list here. The most common misconception about ServicedComponents is that they require the use of COM/Interop and really everyone has bought into that belief. And it is simply wrong." "The Enterprise Services team went a long and very smart way to separate COM Marshaling from COM Transport when they built System.EnterpriseServices and they've done it in such a smart way that only a few people seem to see that they did it. In fact, ServicedComponents make COM transport (including the LRPC mapping) an alternative way of transport that's deeply integrated with the Remoting infrastructure. However, the difference is that ServicedComponent will bypass the channel architecture and replave that with the COM channel architecture: COM/Interop marshaling does not happen for ServicedComponents." 5:03:33 AM

© Copyright 2002 Sam Gentile.