Content deleted Content added
Addressed the {{Advert}} issue. Others before me seem to have done a good job of it. Added an {{Outdated}} tag. Removed one dead link from the "External links" section. Tag: COI template removed |
Source updates |
||
Line 34:
Before Windows 8, programs were identified by their static [[computer icon]]s. The [[Windows Shell#Taskbar|Windows taskbar]] was responsible for representing every app that had a window while running. Metro-style apps, however, are identified by their "tiles" that can show their icon and also other dynamic contents. In addition, in Windows 8 and [[Windows 8.1]] RTM, they are not shown on the Windows taskbar when they run, but on a dedicated app switcher on the left side of the screen.<ref>{{cite web|title=Switch between open apps|url=http://www.microsoft.com/surface/en-us/support/apps-and-windows-store/how-to-switch-between-apps?lc=1033|work=[[Microsoft Surface]] manual|publisher=[[Microsoft]]|access-date=31 December 2013}}</ref> [[Windows 8.1 Update]] added taskbar icons for Metro-style apps.<ref>{{cite web |last=Fitzsimmons |first=Michelle |title=Windows 8.1 Update 1: hands on with Microsoft's latest Windows update |url= http://www.techradar.com/news/software/operating-systems/windows-8-1-update-1-what-s-in-microsoft-s-latest-windows-update-1232863 |work=[[TechRadar]] |publisher=[[Future plc]] |access-date=May 19, 2014 |date=May 13, 2014}}</ref>
There is no set limit on how many copies of desktop apps can run simultaneously. For example, one user may run as many copies of programs such as [[Windows Notepad]], [[Paint (software)|Paint]] or [[Firefox]] as long as the system resources can support. (Some desktop apps, such as [[Windows Media Player]], have extra code that prevents spawning more than one instance.) However, in Windows 8, only one copy of Metro-style apps may run at any given time. True multi-instancing of these apps were not available until Windows 10 version 1803 (released in May 2018).<ref name="multi-instancing">{{cite magazine|last1=Whitechapel|first1=Andrew|title=Universal Windows Platform - Closing UWP-Win32 Gaps|url=https://
== In Windows 10 and Windows 11 ==
Line 49:
=== Licensing and distribution ===
UWP apps can be downloaded from [[Windows Store]] or can be [[Sideloading|sideloaded]]. The sideloading requirements were reduced significantly from Windows 8.x to 10, but the app must still be signed by a trusted [[digital certificate]] that chains to a [[root certificate]].<ref>{{cite AV media |last1=Sheehan |first1=John |first2=Peyman |last2=Zanjani |date=30 March 2016 |title=Project Centennial: Bringing Existing Desktop Applications to the Universal Windows Platform |medium=Video |work=Microsoft Build 2016 Conference |url=https://
==Lifecycle==
Metro-style apps are suspended when they are closed; suspended apps are terminated automatically as needed by a Windows app manager. Dynamic tiles, background components and contracts (interfaces for interacting with other apps) may require an app to be activated before a user starts it.<ref>{{cite web|last1=Joshi|first1=Bipin|title=Understanding Windows Store App Lifecycle and State Management|url=http://www.codeguru.com/win_mobile/win_store_apps/understanding-windows-store-app-lifecycle-and-state-management.htm|website=Code Guru|publisher=[[QuinStreet]]|date=22 February 2013}}</ref><ref>{{cite web|last1=Hale|first1=David|title=
Invoking an arbitrary Metro-style app or UWP app from the command line was first introduced in the [[Windows Insider|Insider]] build 16226 of Windows 10,<ref>{{cite web|last1=Whitechapel|first1=Andrew|title=Command-Line Activation of Universal Windows Apps|url=https://blogs.windows.com/buildingapps/2017/07/05/command-line-activation-universal-windows-apps/|website=Building Apps for Windows|publisher=[[Microsoft]]|date=5 July 2017}}</ref> which was released on 21 June 2017.<ref>{{cite web|last1=Sarkar|first1=Dona|title=Announcing Windows 10 Insider Preview Build 16226 for PC|url=https://blogs.windows.com/windowsexperience/2017/06/21/announcing-windows-10-insider-preview-build-16226-pc/|website=Windows Experience Blog|publisher=[[Microsoft]]|date=21 June 2017}}</ref>
Line 59:
===Windows Runtime===
Traditionally, Windows software is developed using the [[Windows API]]. Software has access to the Windows [[API]] with no arbitrary restrictions. Developers were free to choose their own [[programming language]] and [[development tool]]s. Metro-style apps can only be developed using [[Windows Runtime]] (WinRT). (Note that not every app using WinRT is a Metro-style app.) A limited subset of WinRT is available for also conventional desktop apps.<ref>{{cite web|title=Windows Runtime 8.x APIs for desktop apps|url=https://
Metro-style apps can only be developed using Microsoft's own development tools. According to Allen Bauer, Chief Scientist of [[Embarcadero Technologies]], there are APIs that every computer program must call but Microsoft has forbidden them, except when the call comes from Microsoft's own [[Visual C++]] runtime.<ref>{{cite web|last=Grange|first=Eric|title=Why no native WinRT support in Delphi XE3?|url=http://www.delphitools.info/2012/08/23/why-no-native-winrt-support-in-delphi-xe3/|work=DelphiTools|access-date=13 January 2014|date=23 August 2012}}</ref><ref>{{cite web|last=Anderson|first=Tim|title=Third-party compilers locked out of Windows Runtime development|url=http://www.itwriting.com/blog/6347-third-party-compilers-locked-out-of-windows-runtime-development.html|work=Tim Anderson's ITWriting|access-date=13 January 2014|date=23 August 2012}}</ref><ref>{{cite web|last=Bauer|first=Allen|title=HTML5 Builder|url=https://forums.embarcadero.com/message.jspa?messageID=484319#484319|work=Embarcadero Developer Network|publisher=Embarcadero Technologies|access-date=13 January 2014|date=22 August 2012|archive-date=14 June 2020|archive-url=https://web.archive.org/web/20200614102211/https://forums.embarcadero.com/message.jspa?messageID=484319#484319|url-status=dead}}</ref>
| |||