WinFX December CTP Released

The December CTP of WinFX has been released this morning along with some other related downloads. In addition to the WinFX Runtime Components and the Windows SDK (which has subsumed the WinFX SDK that used to be available separately), you can also download the—hold your breath while you read this one—Visual Studio Code Name "Orcas" CTP WinFX Development Tools...whew! The most exciting part of this last download is the inclusion of "Cider," the Windows Presentation Foundation designer for Visual Studio; how appropriate for the team to deliver Cider for the holiday season!

These bits are compatible with Windows XP SP2, Windows 2003 Server SP1, and the Windows Vista December CTP that was also released today to MSDN Univeral Subscribers and beta testers. You can find more information in the release notes. Tom Archer's post on the subject also points to a Get the Beta page that includes installation instructions and a link to the handy WinFX Runtime Components Uninstall Tool.

And if you're wondering, I will be releasing an updated version of my Adobe Illustrator to XAML Export Plug-In that's compatible with the WinFX December CTP. I'll post a new blog entry when that happens.

Comments (5)
  1. Adam says:

    Ok, i don’t get this. VS2005 (whidbey-based) is supposed to be sufficient for developing indigo/winfx apps right?

    So why do i need a Orcas toolset?

  2. mswanson says:

    Adam: great question. You can certainly develop WinFX applications using Visual Studio 2005. The download above contains technology that is currently scheduled to become available around the time of our next Visual Studio release, code named "Orcas." Specifically, the "Cider" visual designer is timed to that release. This CTP simply adds an early version of the Cider designer to Visual Studio 2005.

  3. Dieter says:


    When i create a new Windows WPF application i get the following errors in VS.NET 2005. The designer window is not shown. This is the final VS.NET 2005 release

    Error 1 Error at element ‘Button’ in markup file


    : Cannot convert the string ‘ApplicationCommands.Open’ in attribute

    ‘Command’ into an object of type ‘System.Windows.Input.ICommand’..

    D:TempWindowsApplication3WindowsApplication3MyApp.xaml 1 1


    Warning 2 Could not read state file

    "objDebugResolveAssemblyReference.cache". Attempting to deserialize an

    empty stream. WindowsApplication3

    Error 3 Could create an instance of type Window

    D:TempWindowsApplication3WindowsApplication3Window1.xaml 1 1


    this is a normal application without any controls

    kind regards


  4. Walterst says:

    “Cider” the Windows Presentation Foundation designer for Visual Studio – in the “Visual Studio Code…

Comments are closed.

Skip to main content