ink
Mon Apr 28 09:47:19 CDT 2008
Thanks Christopher
I have used a developer certificate from the Windows MobileDevice SDK as
suggested.
Thanks.
"Christopher Fairbairn" <christopher@christec.co.nz> wrote in message
news:evRDcmSqIHA.1772@TK2MSFTNGP03.phx.gbl...
> Hi,
>
> ink wrote:
>> Every time the debugger starts up the EXE on the device a warning pops up
>> asking am I sure I want to do this. This seems to happen for all ne
>> assemblies as well and any applications that are shelled from with in my
>> application that I have added to the device.
>
> By the sounds of it this prompt will be the "unsigned app" prompt which
> prompts you that the new executable is untrusted and would you like to
> continue running it at your own risk.
>
> You need to sign your application's executables (*.exe and *.dll's
> essentially) with a certificate to avoid this prompt.
>
> The "Windows Mobile 5.0 Application Security" article available on MSDN at
>
http://msdn2.microsoft.com/en-us/library/ms839681.aspx may be of help to
> you in understanding this model.
>
> You should be able to find some developer certificates within the Windows
> MobileDevice SDK which will help you while developing your application,
> and the article will explain the process to obtain a proper certificate
> when you go about deploying your application for real.
>
> There is also the Device Security Manager PowerToy for Windows Mobile 5.0
> available at
>
http://www.microsoft.com/downloads/details.aspx?FamilyID=7e92628c-d587-47e0-908b-09fee6ea517a&DisplayLang=en
> (also available in newer Device SDKs or built into Visual Studio 2008)
> which allows you to determine the current security configuration of your
> device and alter it if your device will allow it.
>
> Hope this helps,
> Christopher Fairbairn