Re: Silent install on WM5
Source:
http://www.tech−archive.net/Archive/PocketPC/microsoft.public.pocketpc.developer/2005−09/msg00591.html
From: "Robert Levy [MS]" <rlevy@xxxxxxxxxxxxxxxxxxxx>
•
Date: Thu, 22 Sep 2005 22:09:20 −0700
•
You could lower the security policy on your devices but I wouldn't recommend
that as a good practice.
For internal apps, the best approach is to generate a certificate, sign your
stuff with it (including anything you get from 3rd parties, and then
provision that certificate to your devices. This way, anything signed with
your internal certificate and running on your internal devices will get the
same treatment as Mobile2Market apps.
Also note that the signature on a CAB is ignored unless all DLLs and EXEs
inside the CAB are also signed.
−−
−Robert Levy
Program Manager, Windows Mobile Developer Experience
http://blogs.msdn.com/windowsmobile
"Robert G." <RobertG@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BFCE9436−1C3A−425C−B449−4B1277780436@xxxxxxxxxxxxxxxx
> Thanks a lot for your answer!
>
> It doesn't necessarily make me happy though, ....
>
> It seems I'm in the same situation as Jon Beets (see his post on
> 9/8/2005):
>
> We are developing a company−internal piece of software which will never
> hit
> the Mobile2Market phenomenon, furthermore we have to install and configure
> the PDA partly using 3rd Party CAB's which probebly won't be signed, at
> least
> not for now, ...
>
> What would you suggest as a 'workable' solution for us:
>
> 1) Send keystrokes and IDOK messages to wceload (not very professional)
> 2) Change the default policy on the device to "Security−Off Device" (is
> that
Re: Silent install on WM5
Re: Silent install on WM5
1
> possible, and if so how ? )
> 3) Via Registrysettings, Filepatches, anything solution is welcome !
> .....
>
> Thanks in advance,
> Robert G
>
>
> "Robert Levy [MS]" wrote:
>
>> My appologies for this not being documented. Fwiw, the next drop of our
>> docs to MSDN will be more clear on this point.
>>
>> On Windows Mobile 5 we have implem