Francisco Figueiredo Jr Activities

Today we released Npgsql 2.1 RC1. This release has very few fixes since Beta1. In fact, only two: Fixed bugs: #141 AlwaysPrepare does not works in some cases. Thanks @avb1987. #153 Fixed wrong comma putting in AddFunctionColumnListSupport(). Thanks @tyler-nguyen. The changelog of the Beta1 is way bigger and has a lot of information about the changes we made since our last stable 2.0.14 release. You should check it out to see what changed and what new features you will get when you use 2.1. We will have the final version release in the beginning of March. Downloads are available on Nuget, github and pgfoundry. You may want to check my previous post  about how to get Npgsql 2.1 beta1. The instructions there also apply to 2.1 rc1. Please, give it a try and let us know what you think. Drop by our user forums  to discuss or send your bug reports to our issues section on github. 

In my last post , I talked about how to use Npgsql 2.1.0 and showed an App.config file which you could use as a template for your applications which use Entity Framework 6. Npgsql 2.1.0 didn't have a stable release yet. It is currently in beta (and shortly in RC). You can download it from the following sources: Nuget As already mentioned, Npgsql 2.1.0 didn't have a stable release yet, so you will need to ask Nuget to install a pre-release version of Npgsql. You do that with the following nuget command: PM> Install-Package Npgsql -Pre If you plan to use Entity Framework 6, you will also need to download the Npgsql.EntityFramework assembly. This is done with the following nuget command: PM> Install-Package Npgsql.EntityFramework -Pre If you plan to use Entity Framework 4.x, you will need to download  Npgsql.EntityFrameworkLegacy . Install it with the following nuget command: PM> Install-Package Npgsql.EntityFrameworkLegacy -Pre ...

UPDATE (2014-05-19): Marek Beneš noticed a problem in the default connection factory config. It is fixed now. Thanks, Marek! UPDATE (2014-02-20): I created a new post explaining how to get Npgsql 2.1.0. Although this post is about EF 6, I'd like to talk about our current situation to support both EF 6 and EF4.x which explain why there are some subtle changes between EF 4.x and EF 6.x App.config settings.  Support for EF versions 4.x and 6.x Sometime after we started to work on Npgsql 2.1.0, we started to add code to support EF6 and decided to reorganize our Entity Framework support code. Shay created a pull request to organize this change and isolate the EF code out of core Npgsql code. The result was the creation of two separated assemblies: Npgsql.EntityFramework.dll for EF6 and above; Npgsql.EntityFrameworkLegacy.dll for EF4.x. Only when using Npgsql with EF6 you will need to reference Npgsql.EntityFramework.dll assembly. This is needed because the EF ...