I had my project written in Silverlight 4. Recently I've reinstalled my system and installed Silverlight 5. But when I re-installed "everything" I got the problem with BusyIndicator. It does look like this control was removed from System.Windows.Controls.Toolkit and attempts to compile my project (targeted still to Silverlight 4) fails with error:
The type 'ToolkitControls:BusyIndicator' was not found.
The namespace is defined as follow:
xmlns:ToolkitControls="clr-namespace:System.Windows.Controls;
assembly=System.Windows.Controls.Toolkit"
I saw a lot of other topics on StackOverflow and see people use this control widely. That sounds like I don't have some toolbox installed or miss any assembly.
I do have the following components installed:
MS VS 2010 SP1
Tools for Visual Studio® 2010 SP1 ( http://www.microsoft.com/en-us/download/details.aspx?id=28358)
Silverlight 5 Toolkit - December 2011 ( http://silverlight.codeplex.com/releases/view/78435)
Do I need something else?
Probably I need to add some reference to my project to have already installed toolboxes linked to my project?
Please advise, any help is very much appreciated!
P.S. Recently found similar problem and solution for WPF ( The type toolkit:BusyIndicator was not found). But in my case I don't know with which assembly to start... I've looked through the GAC and "Program Files\Microsoft Silverlight": can't find any assemblies in that looks like related to Silverlight control toolbox...
I just added the same Tools and Silverlight 5 ToolKit to my Visual Studio installation. I was able to find the BusyIndicator by going to the ToolBox right clicking and then selectin ChooseItems I found it there not enabled.
Namespace = System.Windows.Controls
Assembly Name = System.Windows.Controls.Toolkit
Directory = C:\Program files (x86)\Microsoft SDKs\Silverlight\v5.0\Toolkit\dec11\Bin
Heh, the answer was easy though not really obvious:
I should install toolkit for the 4th Silverlight (http://silverlight.codeplex.com/releases/view/43528)! :)
I instaled nuget package and now working right.
PM> Install-Package SilverlightToolkit-All
Related
I would like to use Snoop WPF to help in developing and troubleshooting my applications' UI. The problem is, when I check the file on Virus Total, it says that it is infected, so I am not allowed to install it at work. Has else had problems with this download? Please see the report from Virus Total:
https://imgur.com/a/PUMvI
Does anyone have any suggestions?
Removed the SnoopInstaller project and after that it passed my company's antivirus scan. So now just build and run from source.
UPDATE:
Needed to install Visual Studio 2008 and sp1 because when you install this also installs all the required C++ redistributables.
Then I actually opened the Snoop.sln file in Visual Studio 2015, changed all of the ManagedInjectorLauncher project to .NET Framework 4.5.2, and started debugging Snoop.
I followed the following link http://msdn.microsoft.com/en-us/library/aa349641.aspx and found out that my WPF version is 3.0.6920.2011 even though I have already installed .Net Framework 4.5 and Visual Studio 2012. How can that be? I can not write XAML to exploit the new features like Ribbon (cannot find it in the toolbox) with current version of WPF. Thanks.
Right click on References in your project in solution Explorer, choose Add Reference, then enter Assemblies -> Framework, find PresentationCore/PresentationFramework. There you can find version used by your projects.
Note that in some cases - for example if you want to use Ribbon presented in newer WPF, you will have to add suitable reference.
There seems to be a problem with support for the Interactivity namespace of Blend 3 in the VS2010 xaml editor. I have the following installed:
VS2010
Blend 3 + Blend 3 SDK
I am trying to compile a demo project that is targeted at .Net 4 Client Profile and has a reference to System.Windows.Interactivity (in the Blend 3 folder).
In the object browser everything appears to be fine. I can also access Interaction.Behaviours from code-behind, but if I put the namespace xmlns:i="http://schemas.microsoft.com/expression/2010/interactivity" in the xaml file and try to use it, the intellisense is blank.
If I copy something in there anyway, the compiler says:
The tag 'Interaction.Behaviors' does not exist in XML namespace 'http://schemas.microsoft.com/expression/2010/interactivity'.
Do I need to install Blend 4 RC or something?
#TomTom and all SDK 4.0 suggestors:
There is a huge killer criteria that prevents many develpers like me from downloading and using SDK 4.0 even if it is for free: It uses .NET 4.0.
You may ask what's wrong with .NET 4.0? Nothing, except as for today (2013-06-13) still many of our customers don't have it installed on their servers (on the clients it's usually no problem). So if you develop software that should also run on servers, you are forced to use .NET 3.5 even if .NET 4.5 would be state-of-the-art.
#everybody
Does anybody have a solution to Andre Luus original question? How must the namespace import in XAML look like in VS2010 if "System.Windows.Interactivity.dll" of Blend SDK 3.5 for WPF is referenced? (Or was <i:Interaction.Behaviors> named differently in 3.5?)
Addendum:
The solution is:
xmlns:i="clr-namespace:System.Windows.Interactivity;assembly=System.Windows.Interactivity"
The answer from adam linked to the Blend SDK 4.0 for silverlight, if you have this problem in WPF programs you should install this version instead.
If you don't have Blend 4, you can just install the Blend 4 SDK by itself to get the current behavior assemblies.
Behavior and MouseDragElementBehavior belong to Microsoft.Expression.Interaction.dll and System.Windows.Interactivity.dll, please add references to those two assemblies and then rebuild your solution.
Get Blend 4 - free upgrade for you. Available for download at Microsoft (get the trial, it will auto-activate after install if Blend 3 is installed).
Installing the NuGet package Microsoft Expression Blend SDK maintained by JetBrains will solve the issue.
Install-Package JetBrains.System.Windows.Interactivity
I am trying to get started doing some Silverlight development. I am interested in learning about the out-of-browser support. I can create and run Silverlight 3 applications just fine. I have confirmed that I have Silverlight 3 instead of Silverlight 3 Beta. I have been able to confirm this because my API list includes Application.InstallStateChanged instead of Application.ExecutionStateChanged.
However, I do not have the option to enable my application to run offline in Visual Studio. I can see this option in this blog post (http://johnpapa.net/silverlight/updated-silvertwit-code-for-msdn-magazine/). Unfortunately, I do not have the option shown or the Reduce XAP size option. I have downloaded the Visual Studio tools from here (http://www.microsoft.com/downloads/details.aspx?familyid=9442b0f2-7465-417a-88f3-5e7b5409e9dd&displaylang=en).
What am I doing wrong?
Thank you!
It looks like John Papa is using a new version of visual studio possibly the VS2010 beta.
Try this tutorial instead
http://wildermuth.com/2009/03/18/Enabling_Out-of-Browser_Support_in_Silverlight_3
or
http://blogs.msdn.com/katriend/archive/2009/07/10/silverlight-3-out-of-browser-applications.aspx
Corrupted Install
It looks like a corrupted install. Try uninstalling and then see Allen Chen's advice here:
http://silverlight.net/forums/t/83226.aspx including:
Silverlight3_Tools.exe /x:c:\temp /u to manually extract the SL 3 files and c:\temp\SPInstaller.exe to verify the tools install.
Use Blend
Also, If you have Blend 3 installed (preview here) you can enable Out of the Browser inside of Blend. See Project->Silverlight Project Options.
One thing might be that your Silverlight developer runtime got corrupted/overwritten. Try installing it once and see if it solves...
http://silverlight.net/getstarted/silverlight3/default.aspx
Just downloaded the Silverlight 3 Toolkit and executed the MSI file.
Now I need to reference the Microsoft.Windows.Controls.dll file but don't know where MSI unpacked it. Can't find it at C:\ or in C:\Program Files. Where might it be?
ok, this post says that all the components should be in the toolbox, e.g. DockPanel, they are for Visual Studio 2008 Professional but not for Visual Web Developer 2008 Express (it has some controls but not DockPanel for instance)
Answer:
Ok, the answer is: reboot and restart everything (until then Silverlight got a AG_E_PARSER_BAD_TYPE error, and brought down both Visual Studio versions and Firefox). After restarting everything, it works fine: the controls are automatically in the toolbox so you just have to drag them in, no need referencing the dll anymore as in Silverlight 2.
It didnt automatically add anything for me for Silverlight Beta 4 Toolkit and Visual Studio 2010 Beta 2.
I followed these instructions. My toolkit bin was located :
C:\Program Files\Microsoft SDKs\Silverlight\v4.0\Toolkit
In addition I had to select additional DLLs for additional toolkit items from those described in the article. I also had to check the checkbox to indicate I actually wanted those items.
There must be a better way! Anyone?
Just in case anyone was wondering, I was :-).
There is a start menu group named "Microsoft Silverlight 3 Toolkit March 2009" with all the relevant info. The toolkit assemblies can be found in "C:\Program Files\Microsoft SDKs\Silverlight\v3.0\Toolkit\March 2009\Libraries"
The July 2009 release of the Silverlight Toolkit added a "Open the welcome page" choice at the end of the MSI setup.
The path names for the July release are also slightly different, but using the Welcome page (a link is also added to the Start Menu), you'll always have a quick method to find 'em.
Checking that box will make sure that a page opens up with details about everything that's installed, including links to all the binaries, themes, the documentation, etc.
Also, since the controls are all referenced through the AssemblyFolderEx registry key, you can add a GAC-style reference in your C# or VB.NET project...
<Reference Include="System.Windows.Controls.Input.Toolkit" />
And that will just work when built on a machine with the Silverlight SDK.
Hopefully it's a step in the right direction.