The-.net framework is a repackaging of the Windows operating system's application interface libraries (API library);
-The. NET Framework is a Java-like virtual machine runtime (Common Language Runtime) that borrows many of the concepts of a Java virtual machine, but the mechanism is more optimized (for example, it has a "deterministic garbage collector" that Java does not have) Mechanism deterministic garbage Collection, forcing resources to be reclaimed at specified points);
-Defines a common intermediate language (Common intermediate Language), in which all languages are compiled first into this CIL so that programs developed in different languages (vb,c#,j#, and so on) can run under the same mechanism and work seamlessly together.
-The. NET Framework is a bridge of operating system services and applications and is an abstraction layer of application software.
What is the. NET framework?
-does not include the new Windows kernel code
-Does not increase the functionality of Windows operating system level, it is just an extension of OS functionality
-Does not speed up windows
So, the. NET framework is primarily a program architecture in which programmers can quickly and efficiently develop high-quality software. But because it is an intermediate layer of abstraction, the. NET Framework-based software is generally slower than programs developed directly for Windows APIs. Just like when you have to build a violation of the building, you have to buy the original building materials, such as bricks, cement, to know how to use bricks and cement into a wall, but now the. NET Framework has provided a lot of flexible configuration of semi-finished parts, including "wall", you directly installed to use it, Quality is often better than buying bricks and mortar walls yourself, but of course this configuration of the "wall" generally does not have your own brick-and-mortar walls for your own appetite.
The. NET Framework is generally better suited to developing desktop software and enterprise-class software that runs on a PC, but may be based on the following two reasons that Microsoft launches the. NET CF (Compact Framework) that runs on mobile devices:
1) Java has long been running on mobile devices J2ME (Java Micro Edition), is a subset of J2SE (Java standard Edition), Microsoft on the product line must compete with it;
2) mobile devices, many enterprise-class systems need to be integrated into mobile devices, so that mobile devices become the terminals of these systems, and many new enterprise-class systems developed for the. NET Framework, the use of. NET CF development of mobile phone programs can be easily integrated into the server-side system ( For example, using. NET Remoting to directly access the server-side. NET app).
On the PC, the. NET Framework went through several generations: from 1.1 to 2.0 to 3.0 so the latest 3.5, it should be noted that these generations of products are not perfectly backwards compatible, that is, you installed. NET 2.0 does not necessarily run software developed for. NET 1.1, And they often have to be loaded at 1.1. But the. NET Compact Framework on PPC is said to be backwards compatible (I've tried 3.5 to run the existing. NET CF software), and you should be able to run software based on any previous version of the 3.5.
. NET CF 2.0 is said to be inefficient, at least a few 2.0 of the software I installed, feeling is relatively slow. 3.5 is said to be optimized a lot, but the problem is, 3.5 just came out not long, for 3.5 of the software is almost no, so there is no way to confirm whether 3.5 is really much faster than 2.0. Just because 3.5 backwards compatible with 2.0 reasons, I myself put 3.5 in order to ensure that in the future can run all the software based on. NET CF.
So I guess a lot of PPC software developers also on the wait-and-see attitude to. NET CF, mobile devices on the software performance requirements are more stringent, this is enough to dare not use the hasty. But it's really handy to develop software with the. NET Framework, especially if Microsoft's. NET development tools are strong, which is where it's more successful.
Some PPC software is sure to install the. NET Compact Framework to support running
This package uses ActiveSync 4.0 and later to update the device, see Windows Mobile Center for more information. Be sure to connect your device before running Netcfsetupv35.msi. If the device is not connected, ActiveSync stores the CAB file until you connect the device before updating. A user who does not use ActiveSync can run a CAB file that matches the device found in the installation folder directly on the device.