Rob Relyea

xaml:Blog

September 2005 - Posts

  • PRS305 - Healthcare demo source posted

    Filed under: ,

    Our team had a fantastic PDC.  I was privileged to be the presenter for the Lap Around WPF.  It was my biggest presentation ever.  ~2000 developers!

    My goal was to communicate the basics of WPF/XAML and to give brief introductions to many of the topics that we had a drilldown presentation later in the PDC.  So the session ended up being lots of code, lots of markup, and lots of concepts...

    Download Demo Source Code
    With this event, I'm starting to create a URL for every major event I do.  On that page, I'll link to the resources (slides, demos and descriptions).  Over time, I'll be able to enhance those demos, listen to feedback/questions about them, and change what I post or how I describe it.

    http://robrelyea.com/events/pdc2005/

    As you are looking at the code, make sure you look at About This Demo for a description of the different files, things I did in a less than perfect way, etc...

    For the demo, I ended up building a subset of the healthcare demo that you may have seen Sanjay and Ben present on Channel 9.

    I've given several presentations like this before.  PDC2003.  Software design reviews.  Sometimes alone, sometimes tag teaming with Chris. It is always fun to balance the description of the platform, reasons behind our design, while trying to build something useful. 

    Minor Demo Hell
    I had one demo snafu that I was able to recover from very early in the talk.  I haven't watched the video yet...but I believe I pressed ctrl-a then ctrl-v when I was viewing window1.xaml.cs instead of window1.xaml.  I wondered...why was intellisense broken in this xaml?  Later I wondered, why don't those tabs work on the top...why did it say I was viewing Window1.xaml.cs.  In the at least 40 times I practiced the demo, that hadn't happened once!  Gotta love it.

     

    Let me know what you think!

    PostTypeIcon
    18,755 Views
  • Getting the PDC CTP of WinFX installed.

    Filed under: ,

    Critical Update (11/18/2005)

    No reason to install the PDC (Sept 2005) CTP of WinFX anymore.  November 2005 CTP is now out!

     

    PDC 2005!

    Having a great time at PDC2005!  Man, am I excited.

    We had the "Ask the Experts" session last night at the pdc.  I sat at the "WPF - XAML" table last night with ChuckJ and Mike Hillberg.  We had some great conversations with a bunch of people last night.  (Ok, really, all week long.)

    So, I have a bunch of things to discuss about the PDC.  I'll split them up in some other posts over the next few days and weeks.

    Wow, great software, but can't we make it easier to install for the developer

    I was very upset when a customer (Michael Kairys) came by last night saying that he was very excited to install everything.  Unfortunately, we handed out >30 gigabytes of softward over 7 dvds and we didn't make it real simple to know the different install scenarios.

    He had installed the wrong version of VS (we handed out their beta2 and rc1)...and couldn't get it uninstalled again.  Luckily, we had the right 3-4 Microsoft employees in the room to help fix the problem.  We're not always hanging around to help fix these problems, so we really have to make setup easier than it is now.  (I don't think improving the instructions is a big enough step.)  But that is what I can do for now...below...

    The Heros

    Dennis Cheng, a great sdet on the WPF team, was able to help fix Michael's machine with the assistance of Jason Sutherland from the VS team.  I also met a very helpful member of the VS Setup team...but I'm blanking on his name now.

    The Steps to get a WinFX development box going

    I'll try to lay it out more clearly...I'll give 2 sets of instructions, 1 for folks with the DVDs from the PDCs.  And 1 for those folks who are just downloading it all off the web.

    Uninstalling old builds of WinFX or Avalon/Indigo (Added this section in Update #4)

    Before installing a new build of WinFX, you should generally remove all the pieces of the last one you installed.
    Generally, uninstalling in reverse order is the way to do it.
    If the visual studio build didn't change since the last release, you don't need to uninstall it, but you should still uninstall VS Extensions for WinFX then WinFX SDK then WinFX.

    Once you've done that, you may want to run this script that Tim Sneath writes about to make sure old WPF builds are really gone.

    PDC DVDs - How to get a WPF development box going (order matters) if you have the DVDs from the PDC

    1. Operating System Required - Windows XP SP2 or Windows Vista 5219 (not Windows Vista Beta1 or 5231)

    UPDATE5: 10/19/2005 - Why doesn't Windows Vista 5231 work with the PDC CTP
    Our goal is to balance getting customers fresh bits with getting them full-featured bits. With this particular build Vista, the WinFX components didn’t line up with the Windows Vista build. But post build 5231 we integrated the WinFX components into our main Windows build tree and our intention is that going forward every Windows Vista build will include the WinFX components.

    UPDATE3: Another important issue that Gerald Beuchelt ran into: When trying to install the VS2005 Beta 2 on Vista, it constantly failed and the installation stopped with an error when trying to install the MSXML 6.0 component. The solution is to install the MSXML 6.0 parser before you install VS 2005 Beta 2. The installer can be found in the VS directory in the subfolder wcu\msxml.

    2. Disk 4 - WinFx CTP installation
    This installs WinFX on the machine...end users (and developers) will need this done.
    WPF (fka "Avalon"), WCF (fka "Indigo"), and .NET Framework 2.0 all get installed with an integrated setup.

    3. Disk 2 - Visual Studio (Beta 2!!!)  (you can also install VC# Express or VB Express - just make sure it is "Beta 2"!) - Sorry, there is currently no build of WinFX that is compatible with RC or RTM builds of VS!  The first CTP of WinFX after September 2005 will be in sync with the final VS 2005.
       (Disk 2, but you have to copy the folder to the HD and install it from there
    Once the install is done, make sure you do step 2 of the VS setup...install Help content - use it offline if you want it to work its best with WinFX SDK content to come later.

    4. Disk 5 - Windows WinFX SDK (Disk 5)
     (In the windows SDK folder)
    This installs a ton of help content (samples, documentation) and some great tools (xamlpad, etc...)

    5. VS Extensions for WinFx (Disk 4)
    This installs Project Templates and Item Templates for Visual Studio.

     

    Off the web - How to get a WPF development box going (order matters) if you are downloading everything from the web.

    1. Operating System Required - Windows XP SP2 or Windows Vista 5219 (not Windows Vista beta1 or Windows Vista 5231)

    UPDATE3: Another important issue that Gerald Beuchelt ran into: When trying to install the VS2005 Beta 2 on Vista, it constantly failed and the installation stopped with an error when trying to install the MSXML 6.0 component. The solution is to install the MSXML 6.0 parser before you install VS 2005 Beta 2. The installer can be found in the VS directory in the subfolder wcu\msxml.

    2. WinFx CTP installation
    This installs WinFX on the machine...end users (and developers) will need this done.
    WPF (fka "Avalon"), WCF (fka "Indigo"), and .NET Framework 2.0 all get installed with an integrated setup.

    3. Visual Studio (Beta 2!!!)  (or you can also install Visual Basic Express  or VC# Express - just make sure it is "Beta 2"!)  Sorry, there is currently no build of WinFX that is compatible with RC or RTM builds of VS!  The first CTP of WinFX after September 2005 will be in sync with the final VS 2005.
    Once the install is done, make sure you do step 2 of the VS setup...install Help content - use it offline if you want it to work its best with WinFX SDK content to come later.

    4. Windows WinFX SDK
    This installs a ton of help content (samples, documentation) and some great tools (xamlpad, etc...)

    5. VS Extensions for WinFx
    This installs Project Templates and Item Templates for Visual Studio.

    6. VS Extension for Windows Workflow Foundation
    This installs the Visual Studio Extensions for WWF, which will let you get started exploring Windows Workflow Foundation.  (Workflow Foundation is also in Office 12, so they will need a separate product that just has workflow's extension...)
       [Thanks to Robert Burke for "adding" these in this post.]

    A few other helpful related posts

    Why matching VS, WinFX and .Net Framework builds is necessary.

    Details about the VS Extensions for WinFX (This was written about November 2004 CTP...I will update...but still likely useful)

    New details about the improved intellisense experience for XAML in the pdc build. (I'm alsoworking on an another update to this schema now...)

    Additional detail after initial post: A few more details to help understand install order dependencies

    Here are the install dependencies that I know of:
    At the very end you must have all 4 things installed.

    These 3 pieces of software only require that any pieces installed before them must have a matching .Net Framework version.
    ======================================================

    VS beta2 – no requirements before install
    WinFX – no requirements before install
    WinFX SDK – no requirements before install

    This piece of software requires that some software be installed before it
    =======================================================

    VS Extensions for WinFX – requires VS beta2, MSDN Help (step 2 of VS install), and WinFX SDK to be installed beforehand.

    2nd Update: Pointer to CTPMadness tool on Channel 9

    This asp.net application and xml data file provide an easier way to understand for any given ctp (winfx, sql, vs, etc...), which other builds are compatible with it:  http://channel9.msdn.com/ctpmadness/ 

    PostTypeIcon
    33,379 Views