R.Ramesh wants your input on the Visual Studio Class Designer:
It has been a couple of months since we shipped Visual Studio 2005 Beta1. A lot of customers have started looking into Class Designer. The initial response has been great. We have also been getting great feedback on features that customers would like to see in the product through the logging of bugs/suggestions at the MSDN Feedback Center. Thanks to all that have participated so far.
James Vastbinder is "smitten" with it:
I've been in a all day walk-through of Visual Studio 2005 Team System. I'm not sure which parts I should be talking about. Since I come mostly from an architecture background - I think I'm mostly taken by the Class Designer.
I have started writing a series of articles explaining how to do source control and the best practices thereof. See below for links to the individual chapters in this series. The Introduction explains my motivations and goals for writing this series.
INBITE is predicting that 2005 will be the Year of the Developer:
What is important about the Visual Studio Team System is that it allows the development process to take place in an integrated system within a truly Integrated Development Environment.
Less than five years ago, I read a Microsoft internal memo called “Sea Urchins”. This paper pushed for using XML as the communication mechanism between services. Since the “Sea Urchins” memo, we have made great progress in describing the how of services. With “Razorbills”, I propose putting a similar effort behind providing a description of the what of services.
Jason Salas has a book review on an SOA-related title:
At the time of this writing, the two topics arguably getting the most press, causing the most stir and generating the most buzz for web services aficionados are service-oriented architectures (SOA) for general audiences, and more specifically within Microsoft circles, Web Services Enhancements 2.0. Author Jeffrey Hasan (of whose work I'm a big fan, notably for his work in "Performance Tuning and Optimizing ASP.NET Applications" (http://www.apress.com/book/bookDisplay.html?bID=135)) paints a masterful picture of both topics in this outstanding work. This is a must-have if you've caught the WSE bug (pun accidentally intended) and need a practical guide to building better web services.