Fixed compilation warnings. Thanks Jon Hanna (jon at hackcraft dot net) for patches.
updated assembly version to beta 2. (version 1.98.2)
[#1002776] The connection string parameter CommandTimeout does't affected on Command.CommandTimeout. Thanks Oleg Ufaev for patch.
Enable System.Transactions support for EnlistTransaction even when enlist=false is set.  (Thanks for the feedback from  Dean Ward)
Clone more properties, most importantly the parameters.  Necessary for entity framework support.
do not prepend a : to the front of the parameter name when no marker is present.  This keeps the name the same as it was set and is required for entity framework support.
Initial bits of Entity Framework support (#ifdef out)
remove entity requirements from project.  (Shouldn't have been comitted before)
wrapped code in #ifdef ENTITIES since this class also uses entity framework classes as Francisco pointed out.
Added support for parameters explicit typing on plain queries (this support was already present when calling functions). Now when sending queries, Npgsql will send the exact typing of the parameters as specified by DbType or NpgsqlDbType enums. This will allow better type matching between client and server. Thanks Jon Hanna, Josh Cooley and Agrinei for heads up. See http://pgfoundry.org/forum/message.php?msg_id=1002944 for more info.
Reverted search_path patch to original as proposed by Andrus Moor with an slightly modification to use = instead of TO. See here: http://pgfoundry.org/forum/message.php?msg_id=1002859 for discussion.

Added check for semicolon (;) in searchpath connection string parameter to prevent from a sql injection attack.

Now, public schema isn't added automatically anymore. User has to add it if she sets search_path in connection string.
[#1010216] Array Handling. Not fully tested by comments welcome
Added support for array datatype. Anything that implements IEnumerable<T> where T is a type already supported by npgsql will be treated the same as T[], anything that implements IEnumerable<U> where U implements IEnumerable<T> will be treated the same as T[,] (but cause an error if it's a "jagged" array, as postgres doesn't support them) and so on. In order to use it, just use an array or IEnumerable<T> as parameter value. Also, you can specify the NpgsqlDbType as an or'ed value to say it is an array: Binary or with other values. E.g. Array of Box is NpgsqlDbType.Array | NpgsqlDbType.Box. Thanks Jon Hanna (jon at hackcraft dot net) for patches. Also thanks Michael Parshin (parshim at gmail dot com) for his help fixing bugs.
Removed verification of NpgsqlDbType.Array when setting NpgsqlDbType property. As BigInt has an enum value of 0, user would have problems if they try to specify an array of bigint because NpgsqlDbType.Array | NpgsqlDbType.Bigint == NpgsqlDbType.Array. This decision was based in the fact that to fix this problem, we would need to change all enum values which would lead to break already compiled clients. Thanks Jon Hanna for discussion about that.
Adding SqlGenerators for entity framework
added support for the COUNT function
Fixed problem when calling functions with inout or out parameters. They
were being incorrectly added with a column list which was complained by
postgresql server: ERROR: 42601: a column definition list is only
allowed for functions returning "record". See
http://pgfoundry.org/forum/forum.php?thread_id=1075&forum_id=519 for
discussion about this. Thanks very much to Anton Andreev (fn30762
at fmi dot uni-sofia dot bg) for his help providing test cases.
Added ArrayHandling.cs to project and changes the build action on NpgsqlMetaData.xml to embedded resource. NpgsqlSchema.GetDataSourceInformation() was throing exception without this fix. Thanks Patrik Husfloen (husfloen at gmail dot com) for patch.
Added information about running nunit tests, searchpath connection string parameter and array support.
Fix Clone method so that type_info doesn't get automatically initialized through the property getter.
More select statement support plus simple dml support