WPF XAML xmlns: assembly not found problem.

i've created a xbap wpf project
and i have problem with "Error 2 Assembly '' was not found. The 'clr-namespace' URI refers to an assembly that is not referenced by the project. " at the line which highlighted with red color.

CustomControlLibrary2 in particular is a custom control made by using adding wpf control library template project.

<Page x:Class="CarouselSample.Page1"
xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
xmlns:d="http://schemas.microsoft.com/expression/interactivedesigner/2006"
xmlns:mc="http://schemas.openxmlformats.org/markup-compatibility/2006"
mc:Ignorable="d"
xmlns:common="clr-namespace:Common;assembly=Common"
xmlns:mcl="clr-namespace:MyControls"
xmlns:cust="clr-namespace:CustomControlLibrary2;assembly=CustomControlLibrary2"
xmlns:local="Local"
Loaded="OnLoaded"
Background="Black"
Initialized="OnInitialized"
Title="Page1"
>

What is assembliy
how do i fix them

Answer this question

WPF XAML xmlns: assembly not found problem.

Jeroen Alblas
This does not resolve the issue within our project. Still receiving the Assembly '' was not found. The clr-namespace URL refers to an assembly that is not referenced by the project. I guess we will need to wait for an update to the CTP that resolves this issue within the designer.
Cla82
xmlns:common="clr-namespace:Common;assembly=Common"
xmlns:mcl="clr-namespace:MyControls"
These 2 statements reference namespaces in your main assembly. The current CTP of Cider does not support referencing types defined in your main assembly

mark
Dvlnblk
As fas as I know, there will be no future Cider CTP releases for VS 2005. The next CTP releases will be integrated into Orcas. But I hope we won't wait for Orcas for long time.

eriawan
Senkwe Chanda
Try to change the line in AssemblyInfo.cs in your main project so that is has a specific version instead of an automatically created one:

//wrong:

[assembly: AssemblyVersion("1.0.*")]

//better

[assembly: AssemblyVersion("1.0.0.0")]

I think the load errors are because when the xaml is compiled the former executable version number is used, and then when it is linked it gets a new version number and therefore is another assembly for the loader later on.
IamHuM

We are planning include this functionality in Orcas CTPs early next year

mark
sammy chen
thanx for the reply....

so if the main assembly dosent support reference to namespace, how do i solve the problem inorder to use the namespace in the project
i need to include them into this project
is there anyway to work around it
cybertaz69
What CTP will this issue be resolved within, I would like to reference a namespace within the main assembly and use the designer

Regards,

Luke
dfwebbot
Is this just a problem with the designer (Cider) or a general problem with the XAML parser I am trying to use XamlReader with something like <myclass xmlns='clr-namespace:mynamespace'/> and I get an exception about the assembly not being found.

I am just wandering whether I should keep trying or whether I should wait for the next release. Separating the assembly is not really an option since I am writing unit tests that use internal properties.
proecco

Is there a work around for this I am workign with the Patient Monitoring sample and I can not get the designer to work for the XAML.

Thanks,

Tim
KitWest
Is this just a problem with the designer (Cider) or a general problem with the XAML parser I am trying to use XamlReader with something like <myclass xmlns='clr-namespace:mynamespace'/> and I get an exception about the assembly not being found.

From what I understand the XamlReader has the same limitation. I'd suggest you ask on the WPF forum - mark
armindocorreia

The workaround is to either move the classes into a seperate assembly and use them from there or to not use the visual designer - this works fine at runtime.

mark
WPF XAML xmlns: assembly not found problem.

Answer this question