FebCTP clr-namespace problem

Has anyone else had trouble with the new clr-mapping of the FebCTP? I can't
get the most basic of namespace mapping (even within the same assy) working.
Consistent "Assembly '' could not be found." error.

I have Chris Sells' WPF book, and got his latest samples off his site, same
error.

From some other thread, I thought that the problem may be because I used the
uninstall tool to get rid of my JanCTP bits, and some were left over. So I
did complete reinstall on this box of WinXP SP2, all updates, VS2005, then
the FEB beta. Exact same error.

Here's sample XAML code from one of Sells' projects which gives error listed
above:

Thanks,

<Window x:Class="DataBindingDemo.Window1"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:local="clr-namespaceataBindingDemo"
Width="250"
Height="150"
Title="Nick Names">
<Window.Resources>
<Style TargetType="{x:Type TextBlock}">
<Setter Property="VerticalAlignment" Value="Center" />
<Setter Property="FontWeight" Value="Bold" />
<Setter Property="FontStyle" Value="Italic" />
</Style>
<local:Nicknames x:Key="names">
<local:Nickname Name="Don" Nick="Naked" />
<local:Nickname Name="Martin" Nick="Gudge" />
<local:Nickname Name="Tim" Nick="Stinky" />
</local:Nicknames>
</Window.Resources>
<!--<DockPanel x:Name="dockPanel">-->
<DockPanel DataContext="{StaticResource names}">
<StackPanel DockPanel.Dock="Top" Orientation="Horizontal">
<TextBlock>Name: </TextBlock>
<TextBox Text="{Binding Path=Name}" />
<TextBlock>Nick: </TextBlock>
<TextBox Text="{Binding Path=Nick}" />
</StackPanel>
<Button DockPanel.Dock="Bottom" x:Name="addButton">Add</Button>
<ListBox ItemsSource="{Binding}" IsSynchronizedWithCurrentItem="True">
<ListBox.ItemTemplate>
<DataTemplate>
<TextBlock>
<TextBlock Text="{Binding Path=Name}" />:
<TextBlock Text="{Binding Path=Nick}" />
</TextBlock>
</DataTemplate>
</ListBox.ItemTemplate>
</ListBox>
</DockPanel>
</Window>

I'm going through the same issues and was going to post here but looks
like you beat me to it:
http://groups.google.com/group/micro...fe493a8c?hl=en

Brett

Good to know I'm not alone with this problem.

FYI, I posted this as a bug on MSDN product feedback. It would be great for
you to go there and validate the problem, and vote on it as well. This will
server to heighten bug's priority in MS eyes.

http://lab.msdn.microsoft.com/productfeedback/
ID: FDBK48693

Best regards and thank you,
Sean

"brett" wrote:

> I'm going through the same issues and was going to post here but looks
> like you beat me to it:
> http://groups.google.com/group/micro...fe493a8c?hl=en
>
> Brett
>
>

I found that microsoft may change the namespace to

xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"

good luck

"Sean Allison" wrote:

> Good to know I'm not alone with this problem.
>
> FYI, I posted this as a bug on MSDN product feedback. It would be great for
> you to go there and validate the problem, and vote on it as well. This will
> server to heighten bug's priority in MS eyes.
>
> http://lab.msdn.microsoft.com/productfeedback/
> ID: FDBK48693
>
> Best regards and thank you,
> Sean
>
> "brett" wrote:
>
> > I'm going through the same issues and was going to post here but looks
> > like you beat me to it:
> > http://groups.google.com/group/micro...fe493a8c?hl=en
> >
> > Brett
> >
> >

How exactly do I find the bug you reported? I did a search for
existing bug under WPF with the above ID but it didn't find anything.

Brett

These new namespaces break many of the samples posted on the Channel9
Sandbox that make use of vector graphics and really demonstrate the UI.
Does any have suggestions on samples that demonstrate WPF's UI
capabilities using the Feb release of WFP?

Thanks,
Brett

I couldnt work out how to get anywhere with the ID either, but I did manage
to find the bug via other means:

http://lab.msdn.microsoft.com/produc...4-9a9ad149009a

- Doug

> How exactly do I find the bug you reported? I did a search for
> existing bug under WPF with the above ID but it didn't find anything.
>
> Brett
>

Sorry for that oversight Gentlemen. I forgot you have to be registered with
MSDN labs to report bugs to actually search by the ID number.

Thanks Doug, for posting that link for us.
--
Sean Allison


"Douglas Stockwell" wrote:

> I couldnt work out how to get anywhere with the ID either, but I did manage
> to find the bug via other means:
>
> http://lab.msdn.microsoft.com/produc...4-9a9ad149009a
>
> - Doug
>
> > How exactly do I find the bug you reported? I did a search for
> > existing bug under WPF with the above ID but it didn't find anything.
> >
> > Brett
> >
>
>
>

As a side not for those looking to see real XAML apps, I've gotten past
my recent issues at least for the Hands On Labs. Here's what I did:

1.) Download the WinFX Feb CTP:
http://www.microsoft.com/downloads/d...displaylang=en
2.) Download the labs:
http://msdn.microsoft.com/winfx/lear...b/default.aspx
3.) Download the XAML migrate tool:
http://robrelyea.com/tools/XamlMigrate/. (corrects namespace issue)
4.) Run it on these labs from the lab root folder using: XamlMigrate
*.xaml /modeverwrite /s
5.) Build the labs you want to view.

You may have a missing reference for System.Security.Authorization. I
didn't find it mattered either way.

Brett