The .NET Framework 1.1 documentation includes new topics as well as numerous new code examples that illustrate how to accomplish common programming tasks.
The following sections describe some important additions to the version 1.1 documentation.
Secure Coding Guidelines
The new topic Secure Coding Guidelines describes how to avoid common programming errors that lead to insecure and unreliable applications. It also provides information on security practices that are specific to .NET Framework technologies like code access security and security policy.
.NET Compact Framework
The .NET Framework 1.1 documentation includes new information about the .NET Compact Framework. The .NET Compact Framework brings the common language runtime, Windows Forms controls, and other .NET Framework features to small devices. The .NET Compact Framework supports a large subset of the .NET Framework class library optimized for small devices.
Although the .NET Framework 1.1 documentation includes information about the .NET Compact Framework, the .NET Framework SDK does not include the .NET Compact Framework product. The .NET Compact Framework product is included with Visual Studio.
Supported devices include the Pocket PC 2000, Pocket PC 2002, Pocket PC 2002 Phone Edition, and custom-designed embedded devices built with the Windows CE 4.1 operating system. Earlier versions of Windows CE are not supported.
The .NET Compact Framework provides the following key features:
A compact common language runtime that brings the benefits of managed code, such as memory management, code reliability, and language neutrality, to devices.
Consistency with desktop and server programming models.
Seamless connection with XML Web services.
Rich enterprise class data access features with XML classes and ADO.NET.
Classes to program applications that access data using Microsoft SQL Server 2000 Windows CE Edition 2.0.
Full access to native features through platform invoke.
Just-in-time (JIT) compilation for optimal performance.
The Smart Device Projects for Visual Studio are used to develop applications that target the .NET Compact Framework. Smart Device Projects enhance the Visual Basic and Visual C# products with device-specific project types and a form designer to implement .NET Compact Framework Windows Forms controls. You can debug and deploy directly to a device or to Pocket PC and Windows CE emulators.
- Smart Client Developer Center
Provides an information center for smart devices, such as Pocket PC, Smartphone, and other devices running the Windows CE operating system. This information includes facts on service packs for the .NET Compact Framework, FAQs, technical articles, downloads, and training opportunities.
- .NET Compact Framework
Provides a variety of code samples that include using Windows Forms controls, Pocket PC features, custom controls, handling data, using Web services, interoperating with native code, getting the application directory, and determining a Pocket PC identification number.
Applications and controls written for the .NET Framework require the .NET Framework to be installed on the computer where the application or control runs. For the version 1.0 release of the .NET Framework, Microsoft provided one redistributable installer that contains the common language runtime and .NET Framework components that are necessary to run .NET Framework applications. In version 1.1, the new topic Redistributing the .NET Framework provides information about the following subjects:
Download locations for the .NET Framework redistributable, Dotnetfx.exe.
Legal distribution of the .NET Framework.
The minimum configuration requirements for installing the .NET Framework redistributable package.
In addition, this topic contains Dotnetfx.exe Deployment Scenarios. Scenarios include:
Distributing Dotnetfx.exe using an electronic software distribution tool.
Manually installing Dotnetfx.exe from a network share, intranet site, or a Microsoft Web site.
Creating a single setup project to install a .NET Framework application and Dotnetfx.exe.
Primary Interop Assemblies
To create managed applications that interoperate with vendor-supplied, COM-based software, you can use vendor-supplied assemblies called primary interop assemblies. Primary interop assemblies expose a vendor's COM type library to managed applications. Only the library vendor can produce a primary interop assembly, which is signed by the publisher with a strong name. For more information, see Primary Interop Assemblies.
In version 1.1, the new topic Producing Primary Interop Assemblies explains how to name, generate, customize, and distribute primary interop assemblies. Programming with Primary Interop Assemblies explains how to locate, register, and redistribute primary interop assemblies.
Common Language Infrastructure Standard
In the Requirements section of some .NET Framework class library reference pages, the term Common Language Infrastructure (CLI) Standard indicates that the member on that page is specified in ECMA-335 and ISO/IEC 23271 governing the Common Language Infrastructure. This information is provided for the use of developers who might want to restrict their code to members that are part of these Standards. Note that Microsoft does not claim full conformance with these Standards. For more information about ECMA-335, see the ECMA Web site at www.ecma.ch. The ISO standard is expected to be published by December 2002.