I've got VS2010 installed, I've downloaded the Windows Phone add-in and the Silverlight Toolkit from CodePlex, but I cannot work out for the life of me how to actually use the controls in a Windows Phone 7 application...
How do I add the controls into the toolbox, or link them so that the XAML doesn't give me errors all the time? For instance, using the Viewbox - the controls aren't implemented, and the XAML does not compile.
You're probably running into this bug:
http://www.manyniches.com/windows-phone/signed-assemblies-bug-in-the-windows-phone-tools-ctp-refresh/
The Silverlight toolkit wasn't working for me after the April Update.
Did you add a reference to the Silverlight Toolkit assembly in your project?
By the way, Jeff Wilcox has a comprehensive overview of the Silverlight Toolkit controls that work on Windows Phone.
Related
Using VS2015 I upgraded a WP 7.1/7.7 project.
I was developing and testing fine using the 8.1 emulator for a couple of months until I realized that I was missing then newer 8.1 controls in the toolbox.
I started a new separate 8.1 project and I can see a large range of new controls like Listbox and ComboBox that don't exist in the 7.1 upgraded app.
Looking at the project properties the Target Windows Phone OS Version is set to Windows Phone 8.1.
I've searched all over and can't find any other settings to tweak.
The project has the older Windows Phone Toolkit 4.2013.8.16.
I wonder if that blocks the new tools?
How can I get the 8.1 one controls to turn on?
There's two frameworks on Windows Phone 8.1: Silverlight and WinRT. When you upgraded to 8.1, since your project was using Silverlight (WinRT wasn't available on Windows Phone 7), it was set to target Silverlight 8.1. That's why you can't use the WinRT controls. The thing is, WinRT and Silverlight have completely different controls, so you can't automatically convert a project from one to another. You've got to consider whether you really need/want to use WinRT. If so, you'll have to rewrite large portions of your UI code to accommodate with the new controls.
If you want to make the conversion, you should first have a look at the Microsoft documentation to understand the key differences between the two frameworks: https://msdn.microsoft.com/en-us/library/windows/apps/hh452743.aspx
Note that Windows 10 universal apps (the ones that can run on phone and desktop) use WinRT. Silverlight is deprecated, and sooner or later you'll have to upgrade.
I have Installed the Silverlight 5 SDK and I am Trying to Add silverlight Busy Indicator Control to my ToolBox.But I cant Find it in Choose Items ToolBox Window
How Can I Add silverlight Busy Indicator Control to my ToolBox
BusyIndicator exist in the System.Windows.Controls.Toolkit assembly. You must download and install Silverlight 5 Toolkit. After that BusyIndicator must be appeared in ToolBox Window.
Also you can get source codes of Toolkit components.
Silverlight 5 Toolkit download link
Here is the direct link to source code
The Busy Indicator is in the Silverlight Toolkit, not the default Silverlight 5 SDK.
If you download, install, and reference that in your project, you will be able to access System.Windows.Controls.Toolkit.BusyIndicator.
Download Silverlight 5 Toolkit here.
I was watching some video tutorial for developing Windows Phone 7 apps (& hoping to develop Windows 8 apps on that basis ;) The guy in the video tutorial was using Visual Studio 2010 and I have Visual Studio 2012. He created a new project using the option "New -> Project -> Silverlight for Windows Phone". Although I don't have such an option I do have an option called "New -> Project -> Windows Phone". This got me wondering whether there is a difference between those two. Could anybody explain the difference between them, if there is any?
Visual Studio 2010 can only make applications for Windows Phone 7. And Silverlight is the only API available to third-party developers on WP7 (even XNA is based on Silverlight).
With Windows Phone 8 (supported by Visual Studio 2012), new kind of applications were added: native (C++ based), HTML5... That's why calling the category "Silverlight for Windows Phone" didn't make sense anymore, and it was renamed simply "Windows Phone".
It's just a name, it makes no difference to you. When creating a new "Windows Phone app" project, Visual Studio will ask you which version you want to target. If you pick "Windows Phone 7.1", you'll get the exact same API that you had in Visual Studio 2010.
Microsoft only trying to reduce the terminology and popularize certain ways.
Windows phone app is the same as Silverlight for windows phone. the only difference is that Silverlight project in visual studio 2010 targets at the developer choice windows phone 7.0 or Mango (Mango is numbered by the SDK as Windows Phone OS 7.1, while users call it Windows Phone 7.5) or 7.8 according to updates installed. But if you use the windows phone project in visual studio you will target either Windows phone Mango or 7.8 or 8. please note that optional updates may be needed to target some platforms as Windows phone 7.8. windows phone 7.8 is basically a windows phone 7 with some feature backported to it from windows phone 8 as multi size live tiles and some features not backported to it as arabic support.
Silverlight and XNA were completely separate ways to make apps in Windows Phone 7.0. No code silverlight code could be used in a XNA project, nor XNA code could be shared in silverlight project in WP7.0 . Programmers of Windows Phone 7.0 had to know the meaning of each and when to use before choosing. The learn paths of silverlight and xna were too separate that you could learn one and totally ignore the other; in fact most programmers learnt only one of the two. You had to choose your path between the two before implementing a big app, as there is no way back :i.e, no way passing code between the two.
However, starting of Windows Phone Mango, Microsoft introduced Silverlight/XNA. Silverlight/XNA is a new application model for Windows phone Mango. It allows XNA inside Silvelight App. Migrating an XNA game to Silverlight/XNA is not an easy task, but would be rewardable.
Silverlight have UI controls as Textblock and Drop list and have layouts as Grid and stackpanel; so it is easy to make an app in silvelight that look like a form, while XNA is geared toward games , as it is a state based programming . it is very hard to implement a drop list in XNA for most developers.
Silverlight app was renamed to windows phone app to popularize it as a starting point, without having to do a deep thinking in a choice.
Silverlight is a stripped down version of Windows presentation foundation, removing the ability to define your own controls.And Silverlight for windows phone is an even more stripped down version , removing all controls that do not fit on mobile , and removing most of cryptography libraries.
This is the same way microsoft renamed metro-style apps to be windows 8 app, and windows apps to windows forms apps; and then windows forms and WPF were renamed later to Windows desktop apps.
I used C# develop a WP7 app. I'm wondering if the Windows Phone 8 SDK supports WinJS? If so, I will move to WinJS for WP and WinRT both.
No, you can develop an app with HTML5 running in a WebBrowser, but without WinJS. You can use C# on both platforms though. No reason to use WinJS.
To clarify, Windows Phone 8 only supports the Silverlight UI technologies. That is, .NET languages and XAML.
This question may be old, but things have changed as Microsoft is announcing at BUILD 2014 that WinJS is now included in the Windows Phone 8.1 SDK as well.
Build 2014 WinJS on Phone
How to develop an application UI like Metro for Windows Vista/7
github recently released their official client for windows and is very similar to Metro
http://windows.github.com/
You can do it in WPF by retemplating all the controls you use. There seem to be libraries that already do it to make apps look like the Zune Software or the GitHub client.
http://elysium.codeplex.com/
http://mahapps.com/MahApps.Metro/
You can also use Telerik Rad Controls to create WinForms application in metro style theme.
http://www.telerik.com/products/winforms.aspx
Metro UI with Telerik Windows Forms Controls