Pete Batard e4372a9f57 [appstore] don't exit on unhandled parameters ... * Looks like executables installed from the Windows Store launch with a "/InvokerPRAID" added parameter, which of course BREAKS apps that have a defined set of parameters and don't except that Microsoft would gingerly add random unwanted stuff there... * The provision of this extra parameter also appears to be tied to using one of: - <TargetDeviceFamily Name="Windows.Universal" ...> - <uap:SplashScreen ...> - <Application EntryPoint="$targetentrypoint$" ...> in the appxmanifest. * This resulted in our argument processing loop to cause early exit on account that an unexpected option was provided. * Fix this by adding an explicit check for /InvokerPRAID and not exiting on unhandled params and removing or altering the 3 appxmanifest options listed above. * Also set an explicit Windows.FullTrustApplication and remove splash screen. * Also update _pre-commit.sh to update appstore build number automatically. * Also remove splash screen images, add store listing CSV and toggle App builds to manual. * Closes #1690		2021-02-05 17:47:48 +00:00
..
Images	[appstore] don't exit on unhandled parameters	2021-02-05 17:47:48 +00:00
appstore.listing.csv	[appstore] don't exit on unhandled parameters	2021-02-05 17:47:48 +00:00
appstore.wapproj	[appstore] don't exit on unhandled parameters	2021-02-05 17:47:48 +00:00
appstore.wapproj.user	[internal] add Windows AppStore project files	2021-02-04 12:26:27 +00:00
Package.appxmanifest	[appstore] don't exit on unhandled parameters	2021-02-05 17:47:48 +00:00
Package.StoreAssociation.xml	[internal] add Windows AppStore project files	2021-02-04 12:26:27 +00:00
packme.cmd	[dev] add exception for Realtek card readers	2021-01-06 19:27:31 +00:00