.5 MB+ (depends on application) Typical application sizes:
5 - 100 KB 1.31. How do I include imgdecmp.dll in an emulator image?
You must ask the OEM to include it in the device's image. If you are the OEM and you are using Platform Builder 4.2, then including the OS Dependencies for the .NET item automatically causes imgdecmp.dll to be part of the emulator image - if that is not working then refer to cesysgen.bat. Another method is to set the environment variable "__SYSGEN_IMGDECMP=1" to explicitly force the DLL into the image.
1.32. How do I programmatically replace Assemblies in the Global Assembly Cache (GAC)?
One can install and remove Assemblies directly to and from the GAC by programmatically launching cgacutil.
Remove assemblies from the GAC using the -u option
Install assemblies to the GAC using the -i option It is typically safest to remove the Assembly before reinstalling it.
1.33. How can I display Pocket PC applications on my desktop or laptop without needing any device side configuration?
Download the ActiveSync Remote Display from Windows Mobile Developer Power Toys:
1.34. How can I allow Activesync to connect to an Emulator session from Visual Studio .NET 2003?
See the entry titled "11.17. How can I allow Activesync to connect to an Emulator session from Visual Studio .NET 2003?" of this FAQ.
1.35. How can I copy files to the device currently connected to desktop ActiveSync?
See the entry titled "11.18. How can I copy files to the device currently connected to desktop ActiveSync?" of this FAQ.
1.36. How can I stress test user input?
Download Hopper from Windows Mobile Developer Power Toys:
1.37. Where can I get a UI version of the Platform Builder Target Control Window?
Download JShell from Windows Mobile Developer Power Toys:
1.38. Where can I get a Command shell for Pocket PC 2003 devices?
Download PPC Command Shell from Windows Mobile Developer Power Toys:
1.39. How can I get detailed information about currently running processes?
Download RAPI Debug from Windows Mobile Developer Power Toys:
1.40. How can I remotely start an application on a Pocket PC from my desktop?
Download RAPI Start from Windows Mobile Developer Power Toys:
1.41. Why can't I load different assemblies with the same name?
This is by design. You must either change the names of the DLLs, or if the DLLs are strong named, place them in the GAC and use Assembly.Load with a full strong name.
1.42. How can I force Visual Studio .NET 2003 to connect to newer versions of the Pocket PC 2003 emulator?
Download the Emulator ActiveSync Connection Tool from Windows Mobile Developer Power Toys:
This allows ActiveSync to connect to your Emulator session from Visual Studio .NET 2003. Create an ActiveSync session to the 4.2 emulator, this will allow Visual Studio 2003 to consider it a real device (Choose PPC device as the deployment target).
1.43. Why don't my custom controls show up properly in the toolbox?
While adding designer support in Visual Studio .NET 2003 for Smart Device custom controls, you may run into the following issues:
Unable to associate an Icon to the Control for showing it in the toolbox at design time
The component, when added to the toolbox, becomes greyed out Causes
Using a design project separate from the control project. Visual Studio .NET automatically prepends the project default namespace to the bitmap name. The "default namespace" defaults to the project name. This may be a problem because the design project has a slightly different name than the runtime project.
Not setting the correct ToolBoxItemFilterAttribute values Resolutions
Given the following example:
Runtime VS.NET Project: MyProject
Class Name: MyProject.MyClass
Design VS.NET Project Name: MyProject.Design
BitMap name in VS.NET Design Project: Foo.bmp
Bitmap name in design assembly: MyProject.Design.MyClass.bmp
-- This creates a problem because the bitmap needs the name: MyProject.MyClass.bmp
In the above example, setting the design project's default namespace to "MyProject" rather then "MyProject.Design" should fix the problem.
The easiest way to check the name of the bitmap within the assembly is to run ILDASM and open the Manifest. The embedded resources are listed at the end of the manifest.
If you create a custom component derived from the Component class, your code must include the following statements so that your component appears in the Toolbox: ToolBoxItemFilterAttribute("NETCF",ToolBoxItemFilterType.Require)
ToolBoxItemFilterAttribute("System.CF.Windows.Forms", ToolBoxITemFilterType.Custom)
