Silverlight For Windows Phone Download

Posted on  by

WinRT was used for Windows Phone 8.1 apps (although, Silverlight was still possible), and UWP for Windows 10/Windows 10 Mobile apps. An area that a few have complained about as being of particular. Sep 29, 2011  Microsoft Silverlight Edition: Programming Windows Phone 7 Charles Petzold on Amazon.com.FREE. shipping on qualifying offers. NOTE: This book is the printed, Silverlight-focused edition of Programming Windows Phone 7, which is available as a free eBook from the Microsoft Download Center. A Microsoft XNA®-focused edition is also available for sale in print (ISBN 978-0. Download Now. Stream HD Movies, Instantly. Their top-rated Silverlight app for Windows Phone lets you find show times, watch trailers, browse photo galleries, explore popular charts and share movie information. See what you can do. The highest quality interactive video experiences both live and on-demand across multiple formats while. Mar 25, 2013  hello, i have to regularly use www.slateerp.com site from my nokia lumia 620 (wp8). By logging in here. The message displayed: TO VIEW THIS CONTENT, PLEASE INSTALL SILVERLIGHT. When i click to install, it shows:sorry, your phone does'nt support this file type. So now what are the options. Hi, the WP8 browser does not support plugins like. Installing silverlight toolkit for windows phone. Ask Question. I installed it and then started visual studio 2010 for windows phone but when I try to use ListPicker, it seems like this is not available. Browse other questions tagged silverlight windows-phone-7 toolkit or ask your own question.

As Windows Central has been reporting on for several weeks now, Microsoft is not done with its mobile efforts, and internally has already started work on its next attempt at a Windows powered phone platform. For a while now, I've been hearing whispers that Microsoft's next attempt at Windows phone won't include support for older, Windows Phone 8.1 Silverlight based apps, and today more evidence for that has come forward.

Thanks to a screenshot from @gus33000 on Twitter, we can now see that Microsoft has already developed a temporary popup for when a user tries to open a Silverlight app on a build that doesn't support it. The popup says 'Silverlight apps are no longer supported on this version of Windows.' What does this mean for you? It means that when Microsoft is ready to launch its next attempt at Windows on mobile devices, older apps like WhatsApp will not work.

Don't miss out on today's newest and best Black Friday deals
Amazon's Fire Tablet is the one Black Friday purchase you NEED to make!

Now, this doesn't necessarily mean current Windows phone devices will lose support for these apps. It's likely that Microsoft's next attempt at Windows phone won't even launch for existing handsets. Sources suggest Microsoft is going to start afresh with Windows on mobile devices, with UWP being front and center. This is a good thing, as it helps remove older apps that aren't using any new Windows 10 APIs, and forces developers to update their apps or be left behind.

Sorry pic.twitter.com/GOYRZ1ZqtR

— Gustave M. (@gus33000) 2 June 2017

This change should also hopefully directly benefit Windows 10 desktop users too. WhatsApp, for example, now has a choice. Either continue supporting its Silverlight app for Windows Phone 8.1 and Windows 10 Mobile devices, or build a UWP app and bring it to Windows 10 Mobile, Microsoft's next attempt at Windows on mobile handsets, and 500 million Windows 10 PCs. I think the smart choice is pretty obvious.

Windows Central will have more details regarding the future of Windows phone soon. In the meantime, what do you think of this rumored change? Let us know in the comments.

So many choices

Best Xbox One games coming soon — Ancestors, Halo: Reach, and more

Every week, numerous games launch on Xbox One and other platforms. Here are some of the biggest and most anticipated titles launching across Microsoft's platforms next week. In a few days, we'll have a few new smaller releases on Xbox One. Notably, Ancestors: The Humankind Odyssey is finally launching on the console, and Halo: Reach offers an interesting take on the first-person shooter...

-->

If you’re a developer with a Windows Phone Silverlight app, then you can make great use of your skill set and your source code in the move to Windows 10. With Windows 10, you can create a Universal Windows Platform (UWP) app, which is a single app package that your customers can install onto every kind of device. For more background on Windows 10, UWP apps, and the concepts of adaptive code and adaptive UI that we'll mention in this porting guide, see the Guide to Universal Windows Platform (UWP) apps.

Silverlight For Windows Phone Download Free

When you port your Windows Phone Silverlight app to a Windows 10 app, you'll be able to catch up on the mobile features that were introduced in Windows Phone 8.1, and go far beyond them to use the Universal Windows Platform (UWP) whose app model and UI framework are universal across all Windows 10 devices. That makes it possible to support PCs, tablets, phones, and a large number of other kinds of devices, from one code base and with one app package. And that will multiply your app's potential audience and create new possibilities with shared data, purchased consumables, and so on. For more info on new features, see What's new for developers in Windows 10.

If you choose to, the Windows Phone Silverlight version of your app and the Windows 10 version of it can both be available to customers at the same time.

Note This guide is designed to help you port your Windows Phone Silverlight app to Windows 10 manually. In addition to using the information in this guide to port your app, you can try the developer preview of Mobilize.NET's Silverlight Bridge to help automate the porting process. This tool analyzes your app's source code and converts references to Windows Phone Silverlight controls and APIs to their UWP counterparts. Because this tool is still in developer preview, it does not yet handle all conversion scenarios. However, most developers should be able to save some time and effort by starting with this tool. To try the developer preview, visit Mobilize.NET's website.

XAML and .NET, or HTML?

Windows Phone Silverlight has a XAML UI framework based on Silverlight 4.0, and you program against a version of the .NET Framework and a small subset of UWP APIs. Since you used Extensible Application Markup Language (XAML) in your Windows Phone Silverlight app, it's likely that XAML will be your choice for your Windows 10 version because most of your knowledge and experience will transfer, as will much of your source code and the software patterns you use. Even your UI markup and design can port over readily. You will find the managed APIs, the XAML markup, the UI framework, and the tooling all reassuringly familiar, and you can use C++, C#, or Visual Basic along with XAML in a UWP app. You may be surprised at how relatively easy the process is, even if there is a challenge or two along the way.

See Roadmap for Universal Windows Platform (UWP) apps using C# or Visual Basic.

Note Windows 10 supports much more of the .NET Framework than a Windows Phone Store app does. For example, Windows 10 has several System.ServiceModel.* namespaces as well as System.Net, System.Net.NetworkInformation, and System.Net.Sockets. So, now is a great time to port your Windows Phone Silverlight and have your .NET code just compile and work on the new platform. See Namespace and class mappings.Another great reason to recompile your existing .NET source code into a Windows 10 app is that you will benefit from .NET Native, which an ahead-of-time compilation technology that converts MSIL into natively-runnable machine code. .NET Native apps start faster, use less memory, and use less battery than their MSIL counterparts.

This porting guide will focus on XAML but, alternatively, you can build a functionally equivalent app—calling many of the same UWP APIs—using JavaScript, Cascading Style Sheets (CSS), and HTML5 along with the Windows Library for JavaScript. Although the Windows Runtime UI frameworks of XAML and HTML are different from one another, whichever one you choose will work universally across the full range of Windows devices.

Targeting the universal or the mobile device family

Windows

One option you have is to port your app to an app that targets the universal device family. In this case, the app can be installed onto the widest range of devices. If your app calls APIs that are implemented only in the mobile device family, then you can guard those calls with adaptive code. Alternatively, you can choose to port your app to an app that targets the mobile device family in which case you don't need to write adaptive code.

Adapting your app to multiple form factors

The option you choose from the previous section will determine the range of devices that your app or apps will run on, and that may well be a very wide range of devices. Even limiting your app to the mobile device family still leaves you with a wide range of screen sizes to support. So, since your app will be running on form factors that it didn't formerly support, test your UI on those form factors and make any change necessary so that your UI adapts appropriately on each. You can think of this is a post-porting task, or a porting stretch-goal, and there is an example of it in practice in the Bookstore2 case study.

Silverlight Download For Windows Phone

Approaching porting layer-by-layer

Download Microsoft Silverlight Windows 8

  • View. The view (together with the view model) makes up your app's UI. Ideally, the view consists of markup bound to observable properties of a view model. Another pattern (common and convenient, but only in the short term) is for imperative code in a code-behind file to directly manipulate UI elements. In either case, much of your UI markup and design—and even imperative code that manipulates UI elements—will be straightforward to port.
  • View models and data models. Even if you don't formally embrace separation-of-concerns patterns (such as MVVM), there is inevitably code present in your app that performs the function of view model and data model. View model code makes use of types in the UI framework namespaces. Both view model and data model code also use non-visual operating system and .NET APIs (including APIs for to 'using'.Porting for I/O, device, and app modelCode that integrates with the device itself and its sensors involves input from, and output to, the user. It can also involve processing data. But, this code is not generally thought of as either the UI layer or the data layer. This code includes integration with the vibration controller, accelerometer, gyroscope, microphone and speaker (which intersect with speech recognition and synthesis), (geo)location, and input modalities such as touch, mouse, keyboard, and pen.Porting business and data layersBehind your UI are your business and data layers. The code in these layers calls operating system and .NET Framework APIs (for example, background processing, location, the camera, the file system, network, and other data access). The vast majority of those are available to a UWP app, so you can expect to be able to port much of this code without change.Porting for form factor and UXWindows apps share a common look-and-feel across PCs, mobile devices, and many other kinds of devices. The user interface, input, and interaction patterns are very similar, and a user moving between devices will welcome the familiar experience.Case study: Bookstore1This topic presents a case study of porting a very simple Windows Phone Silverlight app to a Windows 10 UWP app. With Windows 10, you can create a single app package that your customers can install onto a wide range of devices, and that's what we'll do in this case study.Case study: Bookstore2This case study—which builds on the info given in Bookstore1—begins with a Windows Phone Silverlight app that displays grouped data in a LongListSelector. In the view model, each instance of the class Author represents the group of the books written by that author, and in the LongListSelector, we can either view the list of books grouped by author or we can zoom out to see a jump list of authors.

    Related topics

    Documentation

    Magazine articles

    Presentations