When To Sysgen, Build, Make Run Time Image, Etc.

Change something in Platform Settings: Makeimg

Change something in a driver in the BSP: Build the driver, Makeimg

Change several things in the BSP: Build the BSP, Makeimg

Change something in the BSP and/or the config files (eg platform.reg): Build & Sysgen the BSP, then Copy Files to RelDir, then Build All Projects and Makeimg.

Change something in the workspace configuration (add or delete a component): Sysgen the platform (and sometimes a clean Sysgen is needed, e.g. when changing from RAM based registry to Hive based Registry).

*Never ever* do a build and sysgen on the build menu. Better yet, right click the menu bar, choose Customize, then click the Build OS menu, select Build & Sysgen and *delete* that option from the build menu.

Hope this helps.

Source: Michel Verhagen

How To: Show File Extension By Default In Windows CE Explorer

Tired of going into Windows Explorer on CE to the view Options and switch on the defaults for showing file extensions and etc., you can achieve the same with adding these registry keys.

Sometimes the Windows CE application developers feel the redundancy of unchecking the default Folder Options Advanced Settings in Windows CE.

We will have to uncheck the options as shown below.

• Do not show hidden files and folders
• Hide protected operating system files (Recommended)
• Hide file extensions

Additionally, you may even include this registry script in Platform Builder for Windows CE to make the settings manifested by default in your Windows CE image.

[HKEY_LOCAL_MACHINE\Explorer]
"ShowSys"=dword:00000001
"ViewAll"=dword:00000001
"ShowExt"=dword:00000001

Hope this helps.

How To: Determine The Executing Application's Path

Did you discovered that

Application.StartupPath;

System.Windows.Forms.Application.StartupPath;

not available in Microsoft .NET Compact Framework?

However, you can get the device application startup path by using the alternative below.

System.IO.Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().GetName().CodeBase);

For more information, please refer to How To: Determine the Executing Application's Path.

Hope this helps!

In The Beginning

Hi,

I'm initiated this weblog after I venture off into development on Microsoft .NET Compact Framework and Microsoft Windows Embedded CE few month ago.

Along my journey on device application development, I did discovered many issues and limitations on Microsoft .NET Compact Framework. However, some limitation can be solved with alternatives methods.

Hopefully, this weblog can be informative and helpful to all device application developers as well as anyone who is curious about Microsoft .NET Compact Framework.

Hope this helps!