Francisco Figueiredo Jr Activities

This is Npgsql 2.2.0 Final Release This release contains 249 commits since the last stable release. Includes bug fixes, improvements and new features. Update notice: If you have been using Npgsql 2.2.0-rc2, you don't need to update to this version. They are the same except for the Assembly version information. Major highlights Visual Studio DDEX support   Kenji Uno added support for DDEX. Now you can use Npgsql with Visual Studio data designer. This is a missing feature a lot of our users requested in the past. Kenji added a tutorial about how to use Npgsql with DDEX. You can find it here: https://github.com/npgsql/Npgsql/wiki/Visual-Studio-Design-Time-Support---DDEX-Provider#install-npgsqlddexprovidervsix   Entity Framework   David Karlaš added support for EFMigration and Database creation in EF6+. Now it is possible to start Code First projects without needing to create a database upfront. EntityFramework and Npgsql will take care of it. Emil Lenngr

This release contains 22 commits since the last release. It contains the following bug fixes: [ #217 ] Impossible to insert a Double.NaN value [ #179 ] NpgsqlCommandBuilder automatic sql commands configuration [ #158 ] NpgsqlCommand.Dispose() should execute "DEALLOCATE " for a prepared command [ #264 ] Mono.Security is outdated [ #296 ] parameter parsing fails (regression) and duplicate [ #240 ] NpgSqlCommand does not substitute parameters when there is a string with escaped apostrophe A complete list of commits for this release can be found here: v2.2.0-beta1...release-2.2.0

The Npgsql Development team is proud to announce that Npgsql 2.2.0 beta1 is now available! This release has the following highlights: Visual Studio DDEX support Kenji Uno added support for DDEX. Now you can use Npgsql with Visual Studio data designer. This is a missing feature a lot of our users requested in the past. Kenji added a tutorial about how to use Npgsql with DDEX. You can find it here . Support for EFMigration and Database creation in EF6+ David Karlaš added support for that. Now it is possible to start Code First projects without needing to create a database upfront. EntityFramework and Npgsql will take care of it. Emil Lenngren added support for a lot of missing features of EntityFramework. Check out this list containing fixes from David and Emil as well as others for EntityFramework. SSLStream support In this release, SSLStream is on by default. If you want to use Mono.Security, you will need to use the following line in your code: NpgsqlC

Achievement unlocked! With the merge of Pull Request #213  (PR #213), Kenji Uno added support for Visual Studio Design Time also known as DDEX.  A most wanted feature From the statistics of pageviews I get from a previous post about design time support, I can affirm that this is a most wanted feature of Npgsql. And I'm very glad to say that Npgsql is finally having it. I'd like to thank Kenji Uno for all his hard work to make this happen.  Npgsql DDEX support is done through an extension file which can be easily installed in Visual Studio. This is a much better situation than we had before where it was needed to use an experimental instance of Visual Studio.  History The code started with wwindcloud in PR #67 and Kenji started to play with it and said he was working to get it usable in VS2012 and 2013 .  Some time later, Kenji said he had some success to get Npgsql DDEX initially working and started to fix the bugs he was finding .  In

This version restores the @@ operator support removed in the previous version. Thanks Glen Parker who provided a fix. Downloads can be found at the usual locations: github download page and the nuget repository . Pgfoundry will be updated soon.

Npgsql 2.1.2 is out! This is a bug fix release. Two fixes are present: KeyNotFoundException when setting ApplicationName on NpgsqlConnectionStringBuilder and  A regression when using NHibernate with queries containing '<' operator. (Less Than' prepare failing). Unfortunately, this fix breaks previous support for @@ operators. So if you need this support, you will have to use the previous 2.1.1 version. Glen Parker is working in a permanent fix. Sorry for this big inconvenience. More info about that can be found at the link above. Please, give it a try and let me know if you have any problems. Please, report your issues in our github issues page .

After a long time, Npgsql 2.1.0 is finally released!  If you have been following my posts about Npgsql 2.1 beta and rc releases, you know we did a lot of changes since our last stable release. The change log for this version is big. You can find a complete list of what has changed and the bugs fixed in the github project release page . It 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. Developers using Npgsql 2.1 and Entity Framework should pay attention to the changes related to new configuration settings. More information about those changes can be checked here . Downloads are available on Nuget , github . pgfoundry downloads will be made available soon. Finally, I'd like to thank some people who did an incredible job and that without them this release wouldn't be possible! Glen Parker has been working in the optimizatio

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

Npgsql has new developers and users communication channels. Shay Rojansky created two new discussion groups for Npgsql: npgsql-dev and npgsql-help . Those groups will be used in place of the Npgsql-devel mailing list and the forums available on pgfoundry.org  respectively. Please, feel free to send your questions and comments to those groups. We hope those groups are very helpful to users looking for Npgsql support.