So far, I have had huge issues with my beta testers: the moment they removed Daily Quote for PocketPC, their PocketPC popped up a highly annoying alert about “File not found” whenever it powered up. Yikes. I have no idea why Windows Mobile can’t purge unneeded notifications like the Palm OS can – but hey, its Windows Mobile…

The ideal solution would involve a single API call being called at program removal: as the program gets kicked off the handheld, a single call is called, thereby eliminating any and all notifications still lingering around. Unfortunately, this is not possible with the .NET CF – the solution is called Setup.dll and requires native code. While I am completely dumbfounded as to why native code is required, the only reason I can think off is that Microsoft wants to make sure that the dll is run even if the .NET framework is not installed.

José Gallardo Salazar has posted a lovely overview of the process to his blog – hit the link below for the full scoop while I try to figure out how it all works:
http://www.mobilepractices.com/2008/10/setupdll-sample-and-walkthrough-terms.html

P.S. A template for a custom Setup.dll can be downloaded here.


Related posts:

  1. Declaring delegates in a single line
  2. Autorun/autostart applications from a memory card on a Windows Mobile device
  3. The relation between Microsoft and foo(enter device maker here)
  4. Microsoft opens WM7 developer program as limitations pop up
  5. Code reuse for Pocket PC and Smartphone