Dec. 24 - Dec. 31 Hot-Fix KB articles Weekly Release - Windows Developer

Hi Everyone,

 

Last week, 11 Developer products related hot-fix KB articles were released, and 3 areforWindows Embedded system, 6 are for Visual Studio, and 2 are for .Net Framework. Below are the details:

 

Windows Embedded system - 3 KB articles:

· 958927 A Windows CE 5.0-based target device that has a network adapter that uses the RealTek RTL8139 device driver may be unresponsive

· 959877  An application may crash when you run the application on a Windows Embedded CE 6.0-based device in some specific scenarios

· 960413  When you run an application that generates a floating-point exception that is compiled by using the /QRfpe command option on a Windows Embedded CE 6.0-based device, you may receive an exception message

 

Visual Studio - 6 KB articles:

· 954885  An empty string is returned when data is retrieved from a varchar (max) column by using SQL Native Client in Visual C++ .NET 2003 SP1

· 957510  Visual C++ 2005 LINK.EXE Linker errors caused by MBCS Symbols

· 957944  You may receive "LNK2001" and "LNK1120" linker errors when you link a project that has MBCS symbols in Microsoft Visual C++ 2005 SP1

· 959378  When you run an application that is built by using the /Ot compiler option in Microsoft Visual Studio 2005 Service Pack 1 (SP1), some "if" statements may run incorrectly

· 959418  The profiling process may crash when you use the instrumentation method to profile an application by using Visual Studio 2005 SP1 on a computer that has .NET Framework 4.0 installed

· 960152  When you try to save a style sheet in Microsoft Visual Studio 2005 Service Pack 1 (SP1), the IDE may shut down unexpectedly

 

.Net Framework - 2 KB articles:

· 954832  You cannot use the mouse to resize a control if you open many forms in Visual Studio 2005 or in Visual Studio 2008 on a computer that is running the .NET Framework 2.0 SP1

· 958252When you use the Msdatasetgenerator custom tool in the .NET Framework 2.0 Service Pack 1 (SP1), the scale value and the precision value in the generated code for a third-party .NET data provider differ from the values that you set

 

Regards,

Content Team