How to get rid of popup warning for new EXE?

  • Thread starter Thread starter ink
  • Start date Start date
I

ink

Hi All

I am developing on an HC700 Motorola HHT. The OS has been upgraded from
PC2003 to WM5. And I am using C# with CF2.

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.

In short any new application that is run on the device for the first time
gets this popup.

How can I stop this? At least for development.

Thanks.
ink
 
Hi,
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/...8c-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
 
Thanks Christopher

I have used a developer certificate from the Windows MobileDevice SDK as
suggested.

Thanks.
 
Back
Top