I wrote in my previous blog why I began to learn about this development. After I made up my mind, I began to look for information. As my younger brother was more than a month ago, I just switched to. net.
. NET architecture only understands the basics and cannot reach the proficient level. Therefore, the lack of basic knowledge makes me not directly go to instance development. I chose the technical knowledge before development.
Supplemented by knowledge, I found the book "microsoft_net compact frame technology insider" on the Internet, and the principles in the book are also clear. Here is the introduction to the course of reading.
The knowledge is summarized, and there is no commercial purpose, just to share with you
Note: The environment in the book is vs2003, because it is relatively early to publish. Here we only understand theoretical knowledge, and now vs2008 will definitely change in this regard.
First, let's figure out the differences between smart device projects and general PC projects:
1. Provides additional tools for connecting to and debugging remote devices.
2. When debugging an application, You must select a device to run the application. You can use a device simulator running on Development Computing, or connect to Development Computing
A physical device.
3. You can generate a cab file for distributing applications from within the device project, instead of creating a separate deployment project.
4. The classes that can be used are different from the classes that can be used for projects created using the complete. NET Framework. You can use the help system integrated by shiy9ong or the Visual Studio object to browse
Device, you can view the classes available in the device project. Function help in vs only lists available classes and class members.
At four o'clock, the first is what is provided, the second is what is needed, the third is what I think is the most important, and the fourth is a tool that can be used.