New version of the Architecture Guidance


I’m a bit tardy in passing this information along, but the Rangers have recently ( April 18th ) released a new version of the Architecture Guidance.

Check out Willy’s post for more details, or go and download it directly here. A bunch of great prescriptive guidance on how to use the modeling and visualization capabilities present in Visual Studio 2010 Ultimate.

Cheers!

Cameron

Comments (5)

  1. Ted says:

    2.5 years have passed since VS 2008 sp1.  Can we get a SP2 anytime soon.  3+ years since XP sp3. Can we get a SP4?

  2. camerons says:

    Is there any chance you can move the VS2010?

  3. Ted says:

    We use VS 2010 for new systems.  For our VS 2008 systems, the time to do a medium product QA prohibits upgrading to VS2010.  Several of our larger systems have a QA cycle taking 6+ man months.  

    An upgrade to VS 2010 for our larger older systems can only be done if there is a large scale new development/rewrite of existing functionality (which is rarely done).  

    We typically develop the initial version and then keep the tool set, OS and database fixed for 5 to 9 years before either rewriting, replacing or decommissioning it.  Service packs are applied during that lifetime.

    A development VM is created for each system as well which is used for post product development and support.  This lets our development team keep current tools on the desktop and older tools (VS2008) in a development VM.

  4. camerons says:

    Ah, got it. Well, I'm afraid we're not planning on a VS 2008 SP2 right now. But if you wouldn't mind following up with me directly, I'd love to discuss any particular issues you were hoping to see corrected on VS2008, as there may be some KB articles or what have you that address those concerns.

  5. How about adding a real String.Format says:

    When will Microsoft upgrade the String.Format to include format of strings (not just numbers?)

    see)

    download.oracle.com/…/formattedtextfield.html

    Character  Description

    U                 Any character (Character.isLetter) All lowercase letters are mapped to uppercase

    L                 Any character (Character.isLetter) All uppercase letters are mapped to lowercase.

    A                 Any character or number (Character.isLetter or Character.isDigit)

    Then the string.format library would be a bit more complete…one could format….a string.

    ex)  MyStr as string = "17TES123456"

    Console.WriteLine("{0:AA-AAA-AAAA},MyStr)

    shows 17-TES-1234

    In this case, contracts define how the string will be formatted for that contract.