Important change: Due to a number of issues with the use of server-side prepared statements, Connector/NET 5.0.2 has disabled their use by default. The disabling of server-side prepared statements does not affect the operation of the connector in any way.

To enable server-side prepared statements you must add the following configuration property to your connector string properties:

ignore prepare=false

The default value of this property is true.

Implemented a stored procedure cache. By default, the connector caches the metadata for the last 25 procedures that are seen. You can change the numbver of procedures that are cacheds by using the procedure cache connection string.

An Ignore Prepare option has been added to the connection string options. If enabled, prepared statements will be disabled application-wide. The default for this option is true.

Creating a connection through the Server Explorer when using the Visual Studio Plugin would fail. The installer for the Visual Studio Plugin has been updated to ensure that Connector/NET 5.0.2 must be installed. (Bug#23071)

Within Mono, using the PreparedStatement interface could result in an error due to a BitArray copying error. (Bug#18186)

Using Windows Vista (RC2) as a non-privileged user would raise a Registry key 'Global' access denied. (Bug#22882)

One system where IPv6 was enabled, Connector/NET would incorrectly resolve hostnames. (Bug#23758)

Column names with accented characters were not parsed properly causing malformed column names in result sets. (Bug#23657)

Connector/NET did not work as a data source for the SqlDataSource object used by ASP.NET 2.0. (Bug#16126)

A System.FormatException exception would be raised when invoking a stored procedure with an ENUM input parameter. (Bug#23268)

During installation, an antivirus error message would be raised (indicating a malicious script problem). (Bug#23245)

An exception would be thrown when calling GetSchemaTable and fields was null. (Bug#23538)