We were definitely excited to see all of the new Mango APIs when they were detailed at MIX '11, which meant that apps could be deeper entwined with the operating system. However we were much more excited about the possibilities for homebrew apps as Microsoft was opening up some key accesses that had thwarted eager developers in the past. But it looks like that excitement was premature and we have now learned that Microsoft is in fact restricting apps even more than before with Mango. According to ChevronWP7 member Rafael Rivera, Mango is going to be restricting apps from making COM calls to the "interop services" found in the operating system's registry and other native resources.
WPCentral's Daniel Rubino attempted to sideload homebrew apps like registry editors and theme changers and was given an error code in response. As Rivera explains it, "Mango won’t officially support the deployment of custom applications with the ID_CAP_INTEROPSERVICES capability flag." So in layman terms, any current homebrew apps that make use of the registry or system access cannot be deployed to the phone thus effectively halting the possibilities for customizations with homebrew.
Mango will still allow apps to be sideloaded via the app deployment tool in the Mango SDK, but don't expect any easy route for developers to create apps with user interface-altering functionality like MobileNotifier for Windows Phone. This pretty much negates everything the development community was excited about with Mango and we really really hope Microsoft is working on that official homebrew plan of theirs.
Via: WMPU, WPCentral
Source: Within Windows
Tidak ada komentar:
Posting Komentar