Use Silverlight for Embedded to develop brilliant interfaces (3)

The previous article is here: Using Silverlight
For Embedded brilliant development interface (2)

The previous article introduced how to develop the se application through subproject, which is too troublesome to develop. In this article, I provide alchemysdk as a supplement to the previous article. This SDK is customized based on the CE 6.0 trial version and can be used for learning and research purposes, you are solely liable for any business activities.

Download from here (2010.5.26 Note: Because the blog space is insufficient, it has been deleted. Build your own SDK .) :
Http://files.cnblogs.com/wangkewei/AlchemySDK.part1.rar
Http://files.cnblogs.com/wangkewei/AlchemySDK.part2.rar

1. Install alchemysdk

 

After the installation is successful, open the device emulator manager to check whether the simulator can be started. (if not, you can download the device emulator manager and install it separately, or open the simulator from Visual Studio ):

 

After connet alchemy emulator, you will find that the simulator is started:

 

2. Fixed SDK errors

Currently, you cannot directly create a se project using alchemysdk. Copy pwinuser. H to the following directory and modify xamlruntime. h to add # include <pwinuser. h>.

If you haven't installed R3, you can download pwinuser. h: http://files.cnblogs.com/wangkewei/pwinuser.zip from here

 

Create a new se application:

 

 

Include the required header file and compile the file to check whether the file is successful. If there is no error, start Code. For details, refer to the previous article: Use Silverlight.
For Embedded brilliant development interface (2)

 

The deployment was successful, but the simulator was in English and displayed as a square when we did not know Chinese:

Next article I will translate about how to create an animation using expression Blend: Using Silverlight
For Embedded brilliant development interface (4)

Author: Wang Kewei
Source: http://wangkewei.cnblogs.com/
Copyright: The copyright of this article is shared by the author and the blog. The detailed link of this article must be noted during reprinting; otherwise, the author will reserve the right to pursue its legal liability.
You can find my article more easily here.