Chris Tacke - Please sir, Just The Facts

March 2010

Sun

Mon

Tue

Wed

Thu

Fri

Sat

Blog Sponsorship

Categories

The opinions expressed herein are my own personal opinions. They are not necessarily fact or sactioned by any other person or organization. If you disagree that's your right. It's also my right to not care.

Tuesday, November 29, 2005

Please sir, Just The Facts

The Crime: My CE device runs a CF app just fine when I deploy it manually, but once I connect to it from Studio for deployment and then cycle the power, not just my app, but all CF apps no longer work. Reflashing the image on the device repairs the sitation. What the hell is going on?

The Evidence:
Article #1: Studio saves connection security info in the device registry
Article #2: Studio saves connection security info in RAM of the device (in the root folder)
Article #3: When a CAB file is expanded, RegFlushKey is called
Article #4: When Studio deploys the CF, it does so as a CAB
Article #5: When a device is reset all RAM is lost
Article #6: The CF requires that the info in RAM and the registry match to launch

Verdict:

When I make a connection some info is stored on the device in RAM and the registry. When I deploy, half that is persisted. When I reset the device or pull power the other half is lost, causing all CF apps to no longer run on the device unless I erase the persistent registry (which depending on your device may mean reflashing the whole damned thing).

Sentence:

Run DelCryptoKeysDevice.exe (part of Windows CE Utilities for Visual Studio .NET 2003 Add-on Pack 1.1) to erase the info from the registry. Doing it on startup by adding it to your image and this to platform.reg means you can forget about it:

[HKEY_LOCAL_MACHINE\init]
"Launch55"="DelCryptoKeys.exe"
"Depend55"=hex:14,00, 1e,00

.NET Compact Framework | CE Device Development

11/29/2005 4:50:47 PM (Eastern Standard Time, UTC-05:00)

Comments [0] |

Name
E-mail
Home page

	Remember Me
Comment (HTML not allowed)
Enter the code shown (prevents robots):