This post originated from an RSS feed registered with .NET Buzz
by Udi Dahan.
Original Post: Disappointed by MS, again
Feed Title: Udi Dahan - The Software Simplist
Feed URL: http://feeds.feedburner.com/UdiDahan-TheSoftwareSimplist
Feed Description: I am a software simplist. I make this beast of architecting, analysing, designing, developing, testing, managing, deploying software systems simple.
This blog is about how I do it.
The other day I was at a presentation at Microsoft Israel given by none other than Hans Verbeek. He was going through some of the finer extensibility points of Visual Studio 2005 (aka Whidbey) and also demo-ing the class designer. To my question as to how the Class Designer supported code generation from sequence diagrams, he replied that there would be no types of diagrams supported besides the class diagram. More specifically, he stated that no support for UML was planned - the "class diagram" was nothing more than a visualization of code. I was disappointed, to say the least. When I first heard of Microsoft's directions in Whitehorse, I thought/hoped that this would be their entrance into the application architecture arena, taking on the likes of Rational/IBM's tool suite. I've got to say, when I saw the "right-click", select "Implement Application" in the Logical Layout Designer jump straight to the code, I didn't know whether to laugh or cry. I seriously can't believe that the architects at Microsoft believe that there is no intermediate step. It could have been that for the release date chosen, the amount of work needed to be done to tackle the full development cycle was too much, so it was decided to cut certain features. I can accept that. What I won't accept is the marketing engine starting to "teach" developers and architects using Microsoft's tools to actually develop systems this way. It's a v1 product. I guess my hopes were too high....
Previous Topic
