WinFx WPF or Avalon - WindowsUIAutomation reference not found
How do you see whether you have a failed WindowsUIAutomation reference in an Avalon project?
Easy, just open up your VS 2005 and create a new Avalon application. You will notice 2 things.
1. Your application cannot compiled.
2. There is an error on refering WindowsUIAutomation
As far I understand, WindowsUIAutomation had been renamed to something else in the latest sdk. I can't be
that specific on the new name, as I still pretty new to Avalon or Windows Presentation Foundation.
So what does this mean? Does it mean you use the wrong version of VS 2005 Beta 2? Not actually...
Basically, I was quite confuse with WinFX SDK installation at first. In order to solve this thing,
I will recommend 2 links as below, as well as extract the necessary information into here:
Extracted from [1] http://www.longhornblogs.com/rrelyea/archive/2005/09/16/PDC2005Software.aspx
Uninstallation
"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." [1]
Okay, once you are done. From the website above, you are recommended to download a javascript file
that helps you to clean the left out avalon references and registry keys.
First download the file from http://www.sneath.org/tim/cleanupSharedFiles.js
Then load up your command prompt in Windows XP, and type cscript cleanupSharedFiles.js.
Thrust me, you need to wait for some time. It took me around 3 -5 minutes. So be patient.
For more information, check out the original blog here
http://blogs.msdn.com/tims/archive/2005/09/20/471815.aspx
Installation
"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!)
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
http://www.microsoft.com/downloads/details.aspx?familyid=ffd636f0-86e9-41e8-9e1c-100a4cc4888f&displaylang=en
This installs WinFX on the machine...end users 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!
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
http://www.microsoft.com/downloads/details.aspx?familyid=C20CC6C8-1F4E-4A5C-BC79-C2FE9ABE69AA&displaylang=en
This installs a ton of help content (samples, documentation) and some great tools (xamlpad, etc...)
5. VS Extensions for WinFx
http://www.microsoft.com/downloads/details.aspx?familyid=EDE1A645-2A53-42E1-8482-3BF1FADADE06&displaylang=en
This installs Project Templates and Item Templates for Visual Studio."
Hope you find this compilation easier, even though you can read it from the URLs above, as it covered
other areas as well. Hope you can get started with it.
Thanks.