Richard Hundhausen has made his name as an author and trainer, teaching quite a number of courses on Microsoft related topics, including ADO.NET and SQL Server. From the interview:
Doug: You seem to be interested in XML Web Services. What are your recommendations on returning data from a web service? Do you use DataSets, custom messages or some mix of the two?
Richard: I support both. If I were building a web service to return inventory information, for example, I would implement a method called GetInventoryDS() and another one called GetInventory(). The first method would be used by anyone consuming my web services from .NET, because they could easily cast the results back into a DataSet object. The second method is a nice, clean XML document, and built for developers who don’t want to see all the Microsoft namespaces in the return data. If I were doing anything custom or tricky, then classes implementing custom serialization would be in order.
Complete interview here.
Douglas McDowell is the Database Geek of the Week this week. Douglas (and you have to like that first name...) is a mentor, solution architect and founder of Atlanta.mdf, a SQL Server User Group in, of course, Atlanta. Douglas is known especially for his deep knowledge of Business Intelligence (BI).
Doug: What are the changes in Visual Studio 2005 that will be most important to BI developers?
Douglas: One-stop shopping, collaboration and deployment. We now have one IDE to do it all, and can even put all our projects into one solution to manage an entire solution build. That leads to collaboration as large, diverse development teams use vehicles such as VSS or Team System to work on components of a solution, decoupled from deployment.
As for deployment, everything .NET developers have had for a few versions is finally at a point where they can do lot of development and debugging without deploying to a server. And once deployed, they have configuration management tools that permit better practices around development, test, QA, stage and production environments. In 2000 and earlier we were jumping through hoops to apply best practices to the Microsoft BI paradigm.
The whole interview is here.