If I tell you, I have to…

Christian Weyer is glad he can finally talk about Indigo, now that he DSG team covers Indigo at this week’s VSLive event.


The link however, brings us to an article on some site called crn, in which we can read the following statements:



  • A CTP of Whidbey Beta 2 will be “issued“ by Microsoft at VSLive this week.
    No idea if they mean they’re gonna talk about it, or hand it out to the visitors. Everyone else however, won’t get their hands on Beta 2 until end March.
  • The CTP will offer “more team system components“ as well as performance improvements
  • Avalon seems to be for Smart clients, so it seems Ernst is right about that one.
    Anyway, Avalon, together with Indigo, should be released “very soon“. Think what you will about that statement.

Microsoft will also give details about some ISV partner tools that will be released.



  • Versant will debut an OR/M tool. Why would Microsoft tell us about this tool? Has it something to do with the drop of ObjectSpaces? Because I still am clueless as to why that has been dropped together with WinFS, as Microsoft said they were tightly coupled.
  • Open Access.NET, some kind of replacement for ADO.NET which should give us developers a lot more speed then with the solutions we can use now. Of course this tool will highly integrate with the still overhyped webservices, so we can all benefit! 😉
  • Eiffel Software is releasing a $1500,- plugin which will give Eiffel developers (in VS2005) multiple-inheritence and, get this, generics.
  • Funny thing, said is that Eiffel is based on a simplified version of UML. Funny, because Microsoft has expanded (or replaced) UML, because (especially) the .NET 2.0 specifications go beyond UML.

All announcements that make you wonder how this will fit into our near future development roads. This OR mapper will probably get a lot of attention and will be known by most, where others might already be way ahead as a tool or as experience. I’d also like to see where Open Access.NET could take us. Almost everyone I see, is using DataSets, which sometimes are definitly not the way to go. Main fault is Microsoft self I think, for providing only small pieces of code as example, and everyone presuming that’s the best practice.


Maybe some people should start up a site where people can share complete problems and their best practice solutions.


Also funny is in a linked article from the first, where some source says that “Microsoft [is] at a great strategic disadvantage in enterprise development” when it comes to their set of tools called Team System. The Rational tools however, aquired by IBM, has the advantage, according to the source, because with Microsoft tools “there’s not a proficient methodological or process base there.
Very funny I think, because the Rational toolset is nothing more then a set of tools, which might support some documentation within RUP. Team System is nothing more, and the methodology is as far or close as you can get, with both sets of tools. My opinion however, is that this is the first version and if it has it faults, Microsoft will eventually get it right. With the fact that the Rational tools are very user unfriendly, and Microsoft tools are really user friendly, looking great with more gimmicks then Rational could ever think of. Microsoft will ‘steal’ or ‘borrow’ a lot of good ideas, but will create such a great toolset, that everyone will eventually drop Rational’s tools. Of course except for these people like in this post.

You may also like...

6 Responses

  1. RJ says:

    Tweakers.net disaggrees :

    Soma Somasegar, vice-president of Microsofts Developer Divisision told today that the next CTP of VS.NEt 2005 will become available this april 🙂

    http://www.tweakers.net/nieuws/36132 (sorry dutch)

    But after reading the source and your interpretation i guess tweakers.net is wrong after all 🙂

  2. Versant’s O/R mapper is in beta for quite some time. It’s one of the most overrated and expensive pieces of software I’ve ever seen. But then again, some people just want to pay way too much for software 😉

  3. Chrissy says:

    Dennis! You are here? I am too. Let’s meet. email me. [email protected] 🙂

  4. @Frans : Hehehehe, I can’t believe them either! Some are even willing to pay to see a product presentation of some large company. I have heard… 😉

    But seriously, never heard of the product. My guess however is, that whenever the product is released, there will be a pretty amount of marketing, also sponsored by Microsoft. Then everyone will believe that’s the product to have, because of the MS "support" and every other OR/M will be judged based on Versant’s tool! 🙂

    Kinda sucks, doesn’t it?! 😉

  5. Erwyn van der Meer says:

    You’ve probably read it elsewhere by now, but in fact Indigo and Avalon WinFX CTP is scheduled to be released before Beta 2 of Visual Studio 2005 and the .NET Framework 2.0. As such the WinFX CTP will be based on a different build of the .NET Framework 2.0. And it also means it will ship with an older build of VS 2005 that is tuned especially for Indigo and Avalon.

    If I interpret the post http://blogs.msdn.com/brada/archive/2005/02/09/369802.aspx by Brad Abrams correctly, the WinFX CTP will be released within the next few weeks.

  6. James says:

    Requirement Management tools will increase requirements definition phase by:

    providing more administrative functions for BA’s

    overcomplicating the simple analyst activities (Adam & eve stages of scratching around drawing models)

    creates more documents

    decreases productivity with unnecessary system burdens

    employing a very user unfriendly interface for end users

    irritating to use, very idiosyncratic

    Other points:

    Respected industry professionals steer clear of these tools (such as Craig Larman)

    Software development is not predictive manufacturing but new product development, therefore re-use at best is negligible

    Low tech tools such as paper and pens are faster, easy to use and can be performed anywhere

    BA’s typically talk, workshop and write up requirements, therefore MS Word is perfect for this

    Customers buy working software, not glossy specs or models

    Facilitates documentation development, not software development!

    Software development is about great people working close, not great tools working for "me".

    In the wash up it won’t improve software end products for customers. People and OO training do!

    Creates:

    beaurocratic steps just to set up and maintain documents

    has many unnecessary "add ins" such as advanced traceability and version control.

    most source code it generates is unusable

    Cons:

    Doesn’t control scope, just creates more hurdles to document and maintain scope

    Are over-priced drawing tools with sub standard workflow

    Is incredibly expensive per staff head

    Conflicts with many departments use of a document repository

Click on a tab to select how you'd like to leave your comment

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.