This article has been archived. It is offered "as is" and will no longer be updated.
The Microsoft .NET Compact Framework 2.0 Service Pack 1 (SP1) is a software update for Microsoft Visual Studio 2005. This service pack includes the following improvements:
New debugging features
Extended platform support
Fixes for several issues
The following features are new in the .NET Compact Framework 2.0 SP1:
Support for Windows CE .NET 4.2 in the .cab installation
An option to install the global assembly cache (GAC) to a storage card
The ability to override the Paint method in a DataGridColumnStyle class has been added. This functionality lets you customize cells in a DataGrid.
Device debugging by using Mdbg.exe
A LogViewer tool for viewing .NET Compact Framework network logs
The .NET Compact Framework Remote Performance Monitor
Support for the [Serializable] attribute
The following issues are fixed in the .NET Compact Framework 2.0 SP1:
A memory leak may occur when you change VT_BYREF variants in managed code.
The current UI culture is incorrectly cached even after you call the CultureInfo.ClearCachedData method.
An uncatchable ObjectDisposedException exception may occur in the HttpWebRequest method when an application exits with asynchronous requests.
Visual Studio stops responding (hangs) when you set a breakpoint in a function. The function must contain an infinite loop and must be called from the Immediate window for this problem to occur.
Breakpoints do not work correctly if the cached managed DLLs on the desktop differ from the DLLs on the device.
The Environment.GetFolderPath method raises an InvalidOperationException exception.
An access violation occurs when you access the Controls property or the Controls.Count property of a control after the control has started the disposing process.
The WebBrowser.DocumentCompleted event is fired in a loop when the DocumentText property contains an image that is inside a table.
Files must be extracted to the main storage to work around hardware issues on some storage cards.
An ArgumentOutOfRangeException exception occurs in the HttpWebRequest method when you access some secure HTTP (https) URLs.
Timers do not work correctly after the tick count wraps around. This issue takes 49.7 days of continuous running to occur.
An error occurs when you use Microsoft ActiveSync to load the .NET Compact Framework 2.0 on a device.
A memory leak occurs when you use Microsoft Component Object Model (COM) marshaling.
The installer does not check for the ActiveSync version. The installer does not disable deployment if the ActiveSync version is earlier than ActiveSync 4.0 build 4343.
An IOException exception is raised in the SerialPort class when you open a serial port on the IPAQ 4150.
A client stops responding (hangs) when you call the HttpWebRequest method over Secure Sockets Layer (SSL). This problem occurs when the payload is larger than 32 KB and the SendChunked property returns false.
An uncatchable exception occurs in the SerialPort class when Bluetooth connectivity is turned off.
A finalizer for the FileStream class causes the application to unexpectedly exit (crash) if a previous input/output operation failed.
The .NET Compact Framework installation fails on devices that have low memory.
A NotSupportedException exception is raised when you use UIntPtr return types in Platform Invocation Services (PInvoke).
The Debug.WriteLine method does not work correctly in the .NET Compact Framework 2.0.
Virtual serial ports are not reported by the SerialPort.GetPortNames method in the SerialPort class.
VARIANT_BOOL types are passed incorrectly on ARMV4I devices when you use COM Interop.
Version comparisons are incorrect when you load assemblies in the .NET Compact Framework 2.0.
The ARMV4 Pocket PC .cab file is large. You should remove the ARMV4I runtime from the ARMV4 Pocket PC .cab file to reduce the size of the .cab file.
Several fixes are added for HTTP abort semantics.
The DateTime.Now method raises an ArgumentOutOfRangeException exception.
When you call the CurrentTimeZone.GetDaylightTime method or the CurrentTimeZone.GetStandardTime method, the device may stop responding. This problem only occurs in rare stress conditions.
For more information about the .NET Compact Framework, visit the following Microsoft Developer Network (MSDN) Web site: