Go to Tim Sneath's Blog to get the links to pull down the January CTP bits.
1. Run uninstall tool - vs_uninst_winfx.exe
2. Run the Winfx setup - winfxsetup.exe
3. Uninstall the Dec SDK
4. Uninstall the Micorosoft Command Shell
5. Install the SDK using a tool like vcdControlTool.exe (just select your .img file)
6. Reboot - this helped me for some reason. You could skip it.
7. Run vsextwfx.msi
8. Read the WinFXReadme.htm where you'll find lovely tidbits like this one below.
IntelliSense in XAML (inside the XML editor):
The Windows Presentation Foundation and XAML schemas provided with the WinFX SDK are not flawless. Today, many things can compile that the schema may not approve of. We also have things that the schema will approve that will not compile.
The schema will complain about attribute values that are not properly cased. Although type converters are generally not case sensitive, XML schema has limitations. We've chosen to put the matching case with the object model in the schema.
DockPanel.Dock="fill"
will compile, but the schema would prefer this form:
DockPanel.Dock="Fill"
ColumnDefinitions and RowDefinitions as direct children inside a Grid will compile and execute fine, but we'd prefer if you use the following syntax today:
<Grid>
<Grid.ColumnDefinitions>
<ColumnDefinition ... />
...
</Grid.ColumnDefinitions>
<Grid.RowDefinitions>
<RowDefinition ... />
...
</Grid.RowDefinitions>
...
</Grid>
Unfortunately, the schema in this release will complain about both ways. In the future, it will not complain if you use the preferred syntax.
Some elements will complain with the "content model is empty" warning. Many times, however, the compiler will be able to handle it.
If you build a custom element (often a custom control), IntelliSense in the XML editor will not work unless you hand build a .xsd for that control and put that .xsd in %programfiles%\microsoft visual studio 8\xml\schemas\
Happy XAMLing,
Sean