3 ms·
Some nits: * Signing packages is not necessary for normal Store distribution. Skip this step. * Devs must work with Microsoft to get their Centennial apps
by withinrafael 10y ago
Some nits:
* Signing packages is not necessary for normal Store distribution. Skip this step.
* Devs must work with Microsoft to get their Centennial apps in the Store right now, it's not a free for all
* There's a swath of users that can't use Centennial apps right now due to a bug that will bugcheck the box.
General Centennial app take-aways:
* Package Win32 apps and throw them in the Store
* You get package update, flighting, analytics and feedback hub integration for free
* Clean install/uninstall due to virtualized file-system/registry writes
- DaiPlusPlus 10y agoSurely something like the Windows app packaging / sandbox model would be implemented in userland - how the heck could it possibly BSOD a machine? That's just astounding.
- withinrafael 10y agoBoils down to kernel drivers using RtlQueryRegistryValues and expecting to access a trusted system hive, not the Centennial redirected one. Oops.
- Hondor 10y agoGood news about signing. I suppose the store itself somehow signs things? Code signing certificates are prohibitively expensive for small developers at around $500.
- withinrafael 10y agoYou upload an .appx with an associated unique identity (allocated via the Windows Dev Center) and Microsoft manages the signing and such on their end.
- garganzol 10y agoAnd you give 30% cut from revenue. Nice played.
- imron 10y agoYou can get them for under $100 a year from some resellers. I got mine from here http://codesigning.ksoftware.net/ http://codesigning.ksoftware.net/ $84 a year, and as low as $67 a year if you go multi-year.