Skip to main content

Microsoft .NET Framework SDK Version 2.0 ReadMe

Thank you for using the .NET Framework SDK version 2.0. We want to make the .NET Framework SDK version 2.0 the best software developer kit ever released, and we need your help to do it. A feedback link is available online. We encourage you to provide us with your comments and requests.

 

This SDK includes new samples demonstrating the latest .NET Framework technology. Samples are located in the SDK documentation, as part of the QuickStart, or in the LateBreaking SDK folder. Samples located in the documentation and LateBreaking folder are also available online in a single zip file from the Download Center.

The .NET Framework SDK includes documentation, sample code, tools, and reference assemblies that enable you to develop code that targets the .NET Compact Framework. To install the .NET Compact Framework reference assemblies and MSBuild files, install the NETCFSetUpV2.msi located in the CompactFramework subdirectory in the SDK. For more information about supported scenarios, see the SDK documentation.

1. System Requirements

The following table lists installation requirements for the .NET Framework 2.0 SDK. For more information, see the System Requirements for Version 2.0 topic in the SDK documentation.

System Requirements for Installing the .NET Framework 2.0 SDK

.NET Framework 2.0 SDK
Processor

Minimum:

600 megahertz (MHz) Pentium processor, or an AMD Opteron, AMD Athlon64 or AMD Athlon XP processor, or an Itanium processor

Recommended:

800 MHz Pentium processor, or an AMD Opteron, AMD Athlon64 or AMD Athlon XP processor, or an Itanium processor

Operating System

x32-bit based systems


Microsoft Windows 2000 Professional with SP4
Windows 2000 Server with SP4
Windows 2000 Advanced Server with SP4
Windows 2000 Datacenter Server with SP4
Microsoft Windows XP Professional with SP2
Windows XP Home Edition with SP2
Windows XP Media Center Edition 2002 with SP2
Windows XP Media Center Edition 2004 with SP2
Windows XP Media Center Edition 2005
Windows XP Tablet PC Edition with SP2
Windows XP Starter Edition
Microsoft Windows Server™ 2003 Standard Edition
Windows Server 2003 Enterprise Edition
Windows Server 2003 Datacenter Edition
Windows Server 2003 Web Edition
Windows Server 2003 R2, Standard Edition
Windows Server 2003 R2, Enterprise Edition
Windows Server 2003 R2, Datacenter Edition

x64-bit based systems

Windows XP Professional x64 Edition
Windows Server 2003, Standard x64 Edition
Windows Server 2003, Enterprise x64 Edition
Windows Server 2003, Datacenter x64 Edition
Windows Server 2003 R2, Standard x64 Edition
Windows Server 2003 R2, Enterprise x64 Edition
Windows Server 2003 R2, Datacenter x64 Edition

Itanium-based systems

Windows Server 2003 with SP1, Enterprise Edition for Itanium-based Systems
Windows Server 2003 with SP1, Datacenter Edition for Itanium-based Systems
Windows Server 2003 R2, Enterprise Edition for Itanium-based Systems
Windows Server 2003 R2, Datacenter Edition for Itanium-based Systems

Minimum Software

.NET Framework 2.0 Redistributable

Microsoft Internet Explorer 6.0 with Service Pack 1

Microsoft Data Access Components (MDAC) 2.8 Service Pack 1

Windows Installer 3.0

RAM

Minimum:

128 megabytes (MB)

Recommended:

256 MB

Hard Disk Space800MB (including 200MB for the .NET Framework Redistributable)
CD or DVD DriveNot required
Display

Minimum:

800 x 600 256 colors

Recommended:

1024 x 768 High Color — 16-bit

MouseNot required

Notes

1. When you start the installer, the default installation location is your system drive. However, you can install the application on any drive. Regardless of the application's location, the installation process installs some files on your system drive. Consequently, if your installation drive differs from your system drive you need to ensure you have sufficient space on both drives.

2. If you are using Windows 2000, you need an unzip utility to access the samples stored in the documentation and the single zip file of samples located at the Download Center.

3. The .NET Framework SDK supports Windows-on-Windows (WOW) on all 64-bit platforms.


2. Known Issues

     2.1 Configuration and Setup

          2.1.1 SQL Server Express is not available for the Itanium-based version of the SDK

 

               Some QuickStart samples that are included with the Itanium-based version of the SDK require sample database use and are configured for use with SQL Server Express.

 

               To resolve or work around this issue

 

               Install the 64-bit version of Microsoft SQL Server 2005 and run

ConfigSamples.exe –sql_instance:<Microsoft SQL Server 2005 Instancename>

from the command line to set up the QuickStart samples to use Microsoft SQL Server 2005.

          2.1.2 Not able to install previously unselected components when repairing the SDK

 

               When you install the SDK, you can select different components to install. When you rerun the SDK setup and select "Repair," you cannot install the previously unselected components.

 

               To resolve or work around this issue

 

               Uninstall the SDK and then reinstall it.

          2.1.3 64-bit SDK can not detect if the hard drive is full during installation

 

               If your designated hard drive is full when you attempt to install the 64 bit SDK, the Setup program will stop responding at "Setup is configuring the install" instead of displaying an error message stating the disk is full.

 

               To resolve or work around this issue

 

               Cancel the Setup program, create the required amount of space on your hard drive, and then reinstall.

          2.1.4 SignTool.exe in the 64-bit SDK displays a CAPICOM version error when executed

 

               If you install the SDK but not Visual Studio 2005 on a 64-bit machine, and if you use SignTool.exe for signing, you will see the following error:

 

               SignTool Error: Signtool requires CAPICOM version 2.1.0.1 or higher. Please copy the latest version of CAPICOM.dll into the directory that contains SignTool.exe. If CAPICOM.dll exists, you may not have proper permissions to install CAPICOM.

 

               The reason for the error is that CAPICOM.dll is not registered correctly.

 

               To resolve or work around this issue

 

               Copy CAPICOM.dll from Program Files\Common\Microsoft Shared\CAPICOM to the SignTool.exe directory.

          2.1.5 ConfigSample.exe fails if Internet Information Server is installed after installing Visual Studio 2005 or the SDK

 

               

ConfigSample.exe will fail if you install the SDK samples in the following order

  1. Install Visual Studio 2005 or the SDK
  2. Install Internet Information Server
  3. Execute ConfigSample.exe to setup the samples for viewing

ConfigSample.exe will fail.

 

               To resolve or work around this issue

 

               
  1. From the SDK command prompt run

    aspnet_regiis.exe -u

  2. Rerun ConfigSamples.exe

     2.2 Samples

          2.2.1 Some samples require Platform SDK headers

 

               The following samples require Platform SDK headers:

CLR Versioning
GCDemo
Callback
ClassMethods
PInvoke

 

               To resolve or work around this issue

 

               You must build these samples using Windows header files. The Windows header files are available either with Visual C++ (using Visual Studio 2005 command prompt with the proper include path set) or by using the Platform SDK and setting the include path. This is because the .NET Framework does not include all the unmanaged headers in Visual C++ and the Platform SDK. You can download the Platform SDK, which includes all the Windows header files, at the Download Center.

          2.2.2 Some samples do not run from the Command window

 

               The following samples do not run in a command environment and must be run within Visual Studio 2005:

Application samples

SecureString

Technology samples

CLR Version Detection

 

               To resolve or work around this issue

 

               1. Open Windows Explorer and navigate to the .exe file (SecureStringConsoleDemo.exe for the SecureString sample and CLRVer.exe for the CLR Version Detection sample) in the sample directory.
2. Double-click the .exe file.

          2.2.3 The SQL CE ResultSet sample requires SQL CE

 

               To use the SQL CE ResultSet sample, a technology sample with the .NET Compact Framework samples, you must install SQL CE, which is included with Visual Studio 2005.

 

               To resolve or work around this issue

 

               Install Visual 2005, which installs SQL CE by default when “smart device projects” is selected during setup.

          2.2.4 Overriding the CPU configuration to build C++ samples using MSBuild

 

               Some C++ samples have a default CPU configuration that differs from what your compiler currently supports, resulting in an error.

 

               To resolve or work around this issue

 

               To build a C++ sample using the 64-bit .NET Framework 2.0 SDK use the following command lines:

For x64-based systems:
Msbuild mySolution.sln /p:Platform=x64

For Itanium-based systems:
Msbuild mySolution.sln /p:Platform=Itanium

To cross compile to target a different platform from the platform you are developing on, you need to install Visual Studio 2005.

          2.2.5 An application sample does not compile

 

               The following sample does not compile because it demonstrates features of the .NET Framework 2.0 that are no longer available.

 

               Application sample
CoopFiber

 

               To resolve or work around this issue

 

               No workaround is available for this sample.

          2.2.6 A technology sample does not compile

 

               The following sample does not compile because it demonstrates features of the .NET Framework 2.0 that are no longer available.

 

               Technology sample
IXmlSerializable (Visual Basic implementation only)

 

               To resolve or work around this issue

 

               Remove the Method attribute in the sample, and rebuild.

          2.2.7 The SQL CLR samples ReadMe has missing entries

 

               The SQL CLR samples directory contains a ReadMe.txt file that does not fully explain how to build and install the samples.

 

               To resolve or work around this issue

 

               The ReadMe.txt for the SQL CLR samples should state that you can use either Visual Studio 2005 or MSBuild in a .NET Framework 2.0 SDK command prompt window to compile the samples, and then you should use SQL Server 2005 Manager Studio, SQL Express Manager, or SQLCMD from a command prompt to execute the installation scripts.

          2.2.8 The Working with Databases in VWD sample in the QuickStart displays an error when sorting the columns

 

               The Working with Database in VWD sample under the Performing Data Access section in the QuickStart displays a "Cannot find column id" error when you try to sort the table by clicking on either the "ID" or the "Name" column header.

 

               To resolve or work around this issue

 

               To fix this error, edit SQLExpress_cs.aspx and SQLExpress_vb.aspx in <sdk Install Path>\QuickStart\aspnet\samples\data with the following:

 

               

Replace the following in both SQLExpress_cs.aspx and SQLExpress_vb.aspx

<Columns>
     <asp:BoundField DataField="ContactID" HeaderText="ID" ReadOnly="True" SortExpression="ID" />
     <asp:BoundField DataField="ContactName" HeaderText="Name" SortExpression="Name" />
</Columns>

with the following

<Columns>
     <asp:BoundField DataField="ContactID" HeaderText="ID" ReadOnly="True" SortExpression="ContactID" />
     <asp:BoundField DataField="ContactName" HeaderText="Name" SortExpression="ContactName" />
</Columns>


Copyright © 2005 Microsoft Corporation. All rights reserved.


Top of Page