Version 1.4.1 of the C# driver is now available.

This is a minor release intended to fix a few issues found in the first
iteration of support for LINQ.

Note: the LINQ implementation has only been tested with C#. We plan to add
unit tests for VB.NET <http://vb.net/> as soon as possible.

The release notes are available online at:

https://github.com/mongodb/mongo-csharp-driver/blob/master/Release%20...

The C# driver is available for download in source or binary form
(.msi installer or .zip file) from:

http://github.com/mongodb/mongo-csharp-driver
http://github.com/mongodb/mongo-csharp-driver/downloads

Note: if you download the zip file, depending on how you unzip the file you
may need to "Unblock" the help file. You can do so by right clicking on the
"CSharpDriverDocs.chm" file and selecting Properties, and then clicking on
the "Unblock" button. You will need to "Unblock" the help file if you see
the message "Navigation to webpage was canceled" where the help text would
normally appear.

The C# driver will also be available soon on NuGet at:

http://www.nuget.org/List/Packages/mongocsharpdriver

Online documentation is available at:

http://www.mongodb.org/display/DOCS/CSharp+Language+Center

The online API reference documentation is available at:

http://api.mongodb.org/csharp/

Note: the online and API reference documentation will be updated to v1.4.1
over the next several days.

Bugs and suggestions can be submitted at:

http://jira.mongodb.org/browse/CSHARP

Questions can be posted on the mongodb-user group:

http://groups.google.com/group/mongodb-user

We monitor this group and will be happy to answer any questions you post
here.

We have fixed the two issues raised by Roman Kuzmin. The related JIRA
tickets are:

https://jira.mongodb.org/browse/CSHARP-446
https://jira.mongodb.org/browse/CSHARP-447

The issue with SetDocumentId caught us by surprise because we thought of
SetDocumentId as an internal method. However, because the interface that
defines SetDocumentId was not implemented privately it leaked out to the
public API of the BsonDocument class. In the next point release we are
temporarily changing the behavior of SetDocumentId back to match 1.4.0 and
earlier for backward compatibility reasons, but at the same time we are
marking these methods as obsolete and intend to make them private in a
later release. The usual way of setting the _id field of a BsonDocument is:

    document["_id"] = value;

The issue with Query.In only occurs if you cast a BsonArray to
IEnumerable<BsonValue> before calling Query.In, so there's a good chance
you won't be affected by that either. See the JIRA ticket CSHARP-447 for
sample code affected by this issue.

Even though both issues appear to be relatively minor and might not affect
too many users, the probability of more users being affected is high enough
that we are planning a 1.4.2 release in the coming week. Both known issues
are currently fixed, and we simply want to wait a few more days to make
sure there are no other minor issues that would be worth addressing in the
1.4.2 point release.

Thanks for the feedback, and please let us know if you have any other
issues or questions.

Robert Stam
10gen

On Wednesday, April 18, 2012 8: