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

Notes

1. When you start the installer, the default installation location is your system drive, which is the drive that boots your system. 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, you should ensure that you have sufficient space is available on your system drive as well as your installation drive if it is different from the system drive.

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

SQL 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 workaround 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 set-up and select "Repair", you cannot install the previously unselected components.

To resolve or workaround this issue

Uninstall the SDK and then reinstall it.

          2.1.3 64 bit SDK can not detect the hard drive is full during install

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 workaround this issue

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

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

If you've installed the SDK, but not Visual Studio 2005, on a 64 bit machine, SignTool.exe, when used for signing, will raise 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.

This is because CAPICOM.dll hasn't been registered correctly.

To resolve or workaround 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

If you install the SDK samples in the following order: Install Visual Studio 2005 or the SDK Install Internet Information Server Execute ConfigSample.exe to setup the samples for viewing ConfigSample.exe will fail.

To resolve or workaround this issue

From the SDK command prompt run aspnet_regiis.exe -u 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

These samples must be built 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 Platform SDK and setting the include path. This is because the .NET Framework does not ship all the unmanaged headers that could be found in Visual C++ and the Platform SDK. You can download the Platform SDK which will include 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.

          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” during setup.

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

Some C++ samples have with a default CPU configuration that is different from what your compiler currently support, 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 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 you are developing on, you need to install Visual Studio 2005.

          2.2.5 Some C++ samples with Project-to-Project does not compile with Msbuild

QuickStart samples All C++ implementations of the Remoting samples under the "How To" section Technology samples Remoting Through Configuration

To resolve or work around this issue

Use VCbuild instead of Msbuild on the solution file to build the sample. For example: VCbuild mySolution.sln

          2.2.6 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 work around is available for this sample.

          2.2.7 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 re-build.

          2.2.8 SQL CLR samples' ReadMe are missing entries

The SQL CLR samples currently have ReadMe.txt file that does not fully explain how to build and install the sample.

To resolve or work around this issue

The ReadMe.txt for the SQL CLR samples should have communicated 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 SQL CLR samples' ReadMe are missing entries

The SQL CLR samples currently have ReadMe.txt file that does not fully explain how to build and install the sample.

To resolve or work around this issue

The ReadMe.txt for the SQL CLR samples should have communicated 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.9 The "Working with Databases in VWD" sample in the QuickStart displays 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 click 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>