![]() For example, in Silverlight applications you would typically find the following using statements: Taking a look at code namespaces, you'll quickly find that a majority of the changes occur in the UI-related classes. You should use the using statement in your WinRT apps instead of clr-namespace, and you should never declare the assembly, as was done in Silverlight applications. Starting with XML namespaces, look at the following highlighted text for Silverlight: XML and code namespaces have changed from Silverlight to the Windows Runtime. The user also has the ability to terminate a WinRT app at any time, but Windows 8 will primarily be managing this. During this time, it's best to use Isolated Storage to persist settings that may benefit the user upon resuming if the user switches back to the app, it's resumed.įinally, if Windows has detected low memory, it might terminate the application while in suspended status. The app has 5 seconds to handle suspension. The application lifecycle of a WinRT app. This app can be suspended when the user switches away from it, or when Windows enters a low-power state.įigure 2. When the user launches a WinRT app, it's quickly up and running. In a WinRT app, this process is managed completely by Windows 8, instead of the user, as shown in Figure 2. The application will continue to run until the browser is closed. Finally, the Silverlight application is rendered inside the browser. The plug-in then downloads the XAP file (which contains the application code) and creates an instance of the Application class, then fires the start-up event. In Silverlight, the user typically types a URL into a browser, and the tag located in the HTML page loads the plug-in. The application lifecycle of a Silverlight app. The Silverlight application lifecycle is shown in Figure 1.įigure 1. The application lifecycle of Silverlight applications versus WinRT apps is very different. A comparison between Silverlight and WinRT apps. Visual Studio 2008 and later can be used, as well as Windows and Mac OSesĭevelopment only via Visual Studio 2012, and only Windows 8 as host OS XNA has been removed however, Direct3D is available in C++ apps Partial support for XNA is available in version 5 Majority of apps written in C#/Visual Basic/XAMLĬ#/Visual Basic/C++/XAML or HTML5/JavaScript/CSS3 are supported Run on top of the Windows Runtime inside Windows 8Ĭan run on Windows/Macintosh/Linux (with support via Moonlight) ![]() As I move between each item in this list, keep these differences in mind. WinRT apps are built primarily for touch input, whereas with Silverlight, a mouse and keyboard are the primary input devices. This opens the platform up to Web developers as well as Silverlight and XAML developers. Windows 8 is more flexible in terms of environments, allowing not only XAML but HTML. Take a look at Table 1 for a quick comparison of each platform's technology. It's important that you first understand the fundamental differences between Silverlight and WinRT apps. In this article, I document 10 things I've found while building my first WinRT app using XAML/C# I hope they'll save you time and energy getting used to this new platform. Because you're already familiar with XAML, you need to understand what the Windows Runtime consists of, and how it's different than what you're used to. Now that the final versions of Windows 8 and Visual Studio 2012 have shipped, most Silverlight developers are looking at ways to translate their existing skill set to Windows Runtime (WinRT) apps built with XAML. In-Depth 10 Things Silverlight Devs Need to Know About the Windows RuntimeĮvery Silverlight developer needs to know these differences between Silverlight and the Windows Runtime before starting on a WinRT app.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |