Why is 'BusyIndicator' not found?

[complete]

Why is 'BusyIndicator' not found?

I am using Silverlight 5 toolkit and I am references that version of Silverlight.Windows.Controls.Toolkit in my silverlight demo.

But I get this error and I do not know what to do

Error 16 The tag 'BusyIndicator' does not exist in XML namespace 'clr-namespace:System.Windows.Controls;assembly=System.Windows.Controls.Toolkit'. C:\Users\Bobbi\Documents\Visual Studio 2012\Projects\...

How do I get the code to compile?

 

[aL Mac]

Error 16 The tag 'BusyIndicator' does not exist in XML namespace 'clr-namespace:System.Windows.Controls;assembly=System.Windows.Co ntrols.Toolkit'. C:\Users\Bobbi\Documents\Visual Studio 2012\Projects\...

It looks like there is a typo in your XML namespace declaration. (remove the space)

 

[Pwyl_The_Destroyer]

That space is added by the message board engine to keep long strings of text from breaking the frame formatting.

 

[aL Mac]

Ah, well I believe you have the wrong namespace then. I've never used the toolkit before. But I believe it is in Microsoft.Windows.Controls. Or you can look to import the XML namespace (which can map multiple CLR namespaces from an assembly).

xmlns:extToolkit="clr-namespace:Microsoft.Windows.Controls;assembly=WPFToolkit.Extended"

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

or

http://schemas.microsoft.com/wpf/2008/toolkit

 

[FreiDOg]

Make sure that you've added project references to
System.Windows.Controls
System.Windows.Controls.Layout.ToolKit
System.Windows.Controls.ToolKit
System.Windows.Controls.ToolKit.Internals

There's some dependencies in the toolkit that (At least in VS2010) don't get added automatically if you just drop controls onto the screen.

As aL Mac says, the standard namespace for the Silverlight toolkit controls is
http://schemas.microsoft.com/winfx/2006/xaml/presentation/toolkit
But the BusyIndicator is in the System.Windows.Controls namespace so it should import the same with how you have it.


The other option is, depending on Windows and Visual Studio settings the assembly may be blocked and VS2012 is declining to import it. To fix that, you'd need to go to where ever you installed the toolkit to, bring up the properties for each of the assemblies you're making use of and unblock them.