Page 1 of 1
Mango a podpora "interopservices"?
Posted: Fri Sep 09, 2011 18:11
by Martin Suchan
Dotaz, Mango nepodporuje nahravani vlastich XAP souboru vyzadujicicih capabalitu ID_CAP_INTEROPSERVICES - tj. ani po unlocku nelze nahrat pomoci XAP installeru TouchXplorer, ani On-Device ProXML 0.7, ani jakoukoliv jinou aplikaci, ktera saha na nativni kod. Nevite nekdo, jak to obejit? Rad bych si pridal do mobilu HTC HD7 s Mangem beta 2 cestinu, ale zadne navody nefunguji,
ani tento, protoze nelze nahrat odkazovane aplikace
Napada me snad, ze Chevron unlock povoluje(?) instalaci i aplikaci s ID_CAP_INTEROPSERVICES, jinak si to neumim vysvetlit.
Mango a podpora "interpopservices"?
Posted: Fri Sep 09, 2011 18:20
by 19roman97
presne to potrebujem aj ja... cestinu mam ale app instalovat nejde
Mango a podpora "interpopservices"?
Posted: Fri Sep 09, 2011 21:04
by Krayzie
Mozno to nakoniec predsa pojde
http://wmpoweruser.com/kddi-contact-tra ... er+User%29" onclick="window.open(this.href);return false;
Mango a podpora "interopservices"?
Posted: Sun Sep 11, 2011 13:26
by Martin Suchan
Zajimave, podle vseho
pouze Samsung mobily umoznuji po unlocku nahravat aplikace vyuzivajici interopservices = jak napsali na XDA:
XDA wrote:The only people I have heard being able to side load INTEROPSERVICES are Samsung users. It is in my opinion that tey're getting an incomplete update process that doesn't properly update pacmaninstaller.exe, which is the exe that installs XAP & has been taken apart & found to have the block for INTEROPSERVICES. All Chevron does is apply a registry change, the same registry change that the official Dev Unlock does. It just uses a custom cert installed through a security hole that was fixed in NoDo.
Jen takovy napad, myslite, ze by mohlo fungovat dynamicke loadovani dllka, ktere by se podarilo propasovat do IsolatedStorage "legalni" aplikace?
-- doplnění předchozího příspěvku (stř zář 21, 2011 13:22) --
Aktualni zjisteni - aby vam fungoval deploy aplikace v Mangu s interop services, je treba nastavit v NoDo "MaxUnsignedApp" na 0x7FFFFFFF , vice zde:
http://forum.xda-developers.com/showthr ... ?t=1265321" onclick="window.open(this.href);return false;
XDA wrote:Interop-unlock: On RTM and NoDo versions of WP7 it was possible to run apps with native code. These apps would use a COM-Interop-Bridge to transit between managed and native code. These apps need to be tagged with the Interop-capability called "ID_CAP_INTEROPSERVICES". These apps don't seem to run on Mango. Not even when you have a legit Developer Unlock. There are two reasons for that. The first reason is that most native libraries need some modifications to run on Mango. I found out how to do this and modified WP7 Root Tools so that it is compatible with Mango. The other reason is a deployment-restriction. That is the Interop-Lock that needs to be Unlocked. If you have a normal Dev-unlock on Mango and you try to deploy an app with that uses COM interop, the deployment will fail with error 0x81030120. Currently, the only known way to get an Interop-Unlock is to revert to NoDo or earlier version, apply unlock-settings there and then use the priously refered thread to update to Mango. The key seems to be the registry setting for MaxUnsignedApp. This value is 0x0a when the device has a normal Dev-Unlock. But when it is set to 0x7FFFFFFF it is possible to side-load apps that use COM interop/native code. The problem is that, to set this setting you already need to run native code, so this setting can't be changed on Mango. Thanks to contable and Marvin_S for their research on this matter. If you need more info on reverting to an older version to apply a working unlock and then upgrade back to Mango, you should look here and here. I will see if I can find a work-around for this problem, so that it will be possible to do an Interop-Unlock on Mango, without reverting to a previous version.