Skip to main content

Npgsql 2.0.13 beta1 released!


Today we released the first beta of Npgsql 2.0.13! 

This new beta release had a lot of bugs fixed and initial support for Entity Framework 6! More information about how to use Entity framework 6 with Npgsql can be found in this post.

Checkout the release notes for more information about the bugs fixed in this release.

Download it from our downloads section.

Important notice about this release


Unfortunately, I made a mistake when updating the assembly version for this release and it was created with a wrong value. I'm very sorry for that.

This release should have been 2.0.12.91 and not 2.0.13.91

Next beta release will have the version value fixed.

What are the implications? 

The biggest problem is that this beta version will have a version number higher than the final 2.0.13 version while this beta version has 2.0.13.91. As it is a beta and it is not supposed to be deployed in production systems, we think this won't give problems to our users. We are very sorry for any problem this may have caused.

How is Npgsql assembly versioned?

In the beginning, we used to use the same assembly version througout all the beta release cycle until the final release.
With this approach, Npgsql 2.0.10 beta1 would have the assembly version of 2.0.10.0 and beta2 would also have the assembly version of 2.0.10.0. This was creating confusion between users because they couldn't differentiate which version they were working with.

Starting with 2.0.11, we changed this in order to identify each version. We started to use the last two parts of the assembly version in order to identify beta releases. 

This way, a beta release was identified in the following form:

  • Npgsql 2.0.11 beta1 would be identified as: 2.0.10.91;
  • Npgsql 2.0.11 beta2 would be identified as 2.0.10.92 and so on. 
With this schema, the beta versions will be incremented towards the final version 2.0.11.0. 


Regarding this 2.0.13 beta1 release, its assembly version should have been 2.0.12.91 and not 2.0.13.91. The former value indicates the assembly is approaching the 2.0.13 while the latter indicates the assembly is approaching 2.0.14 which is not the case.

We hope this won't happen again. :(
Labels:

Comments

Unknown said…
Can download this by Nuget ?
05 July, 2013 13:53
Francisco Junior said…
This comment has been removed by the author.
05 July, 2013 15:46
Francisco Junior said…
I still need to update Nuget with this release. Sorry for that.
05 July, 2013 15:47
Алексей Концевич said…
Any chance to this or next beta in NuGet soon? It has some very important fixes with transactions. Seems we have problems with them.
11 July, 2013 19:19
GLane said…
when u r going to release 2.0.13 stable release.... because when we try out beta version with visual studio 2012, end-up with errors...we cannot even see npgsql data provider inside providers list....This one is pretty urgent, so Please reply..... Thank you
05 August, 2013 04:47
Unknown said…
Nice work. Will give a try for sure!
20 August, 2013 17:48
Unknown said…
Can you point out to some sort of guide to get it ready to use?

I am trying to set it up for use with VS 2012 Express and found out that due Microsoft Licensing restrictions, no provider should be available for EF Design/Diagrams

I have downloaded the Professional/Premium/Ultimate Trial versions of VS 2013 and it not working in Full.

I do can connect to PostgreSQL and access data out there, but I get a lot of Exceptions about dbo schema not existing, absence of __MigrationHistory table and so on.

Since it don´t show as Data Provider for EF Models and Database connections, it will not generate the EF metadata info.

I am going to do a second try with VS2012.

What I did:

1. Downloaded Npgsql2.0.13.91-bin-ms-net4.5eE6.zip (beta)
2. Expanded it
3. Run gacutil -i Npgsql.dll
4. Run gacutil -l | findstr /i Npgsql to check it it was there
5. Created a new project and tried to add a new EF model, but PostgreSQL was not a option there
6. Registered it as an EF provider at , as an Factory Provider at and a Connection at in the app.config file
7. Using NuGet, installed Npgsql (and -Pre) and EntityFramework

I want to use it for Database First option.

What I am missing to get it working with diagrams, ef models, etc?
06 December, 2013 11:24
Post a Comment

Popular posts from this blog

Npgsql Design time support preview available for download!

UPDATE2 : For some reason, Blogger lost the original post. I had to republish it. UPDATE : Jerónimo told me that you  must  use the Npgsql version which is inside the zip file in order to make it work. After so much time (more than I wanted it to take) Npgsql finally has a initial design time support for Visual Studio! This work was done by Jerónimo Milea. Jerónimo let me know he was working on DDEX support on this thread  after I said I was working on DDEX support for Npgsql. He sent me his working copy and I started to play with it. Note that as a preview version many things may not work ok and we wanted you to provide us feedback so we can fix any bugs. You can download the project file from our downloads page . Design time support is provided as a zip file containing support code as well as a copy of Npgsql project file. So, everything you need to start working with design time support is already packaged for you. When you unzip the file, you will have ...
42 comments
Read more

Npgsql Tips: Using " in (...)" queries with parameters list and "any" operator

Hi, all! We have received some users questions about how to send a list of values to be used in queries using the "in" operator. Something like: select foo, bar from table where foo in (blah1, blah2, blah3); Npgsql supports array-like parameter values and the first idea to have this working would try to use it directly: NpgsqlCommand command = new NpgsqlCommand("select * from tablee where field_serial in (:parameterlist)", conn); ArrayList l = new ArrayList(); l.Add(5); l.Add(6); command.Parameters.Add(new NpgsqlParameter("parameterlist", NpgsqlDbType.Array | NpgsqlDbType.Integer)); command.Parameters[0].Value = l.ToArray(); NpgsqlDataReader dr = command.ExecuteReader(); but unfortunately this won't work as expected. Npgsql will send a query like this: select * from tablee where field_serial in ((array[5,6])::int4[]) And Postgresql will complain with the followin...
45 comments
Read more

Initial EF-6 support added to Npgsql

In my last post , I said there is a pull request by Pēteris Ņikiforovs to add support for EF-6 to Npgsql. Yesterday, I merged this pull request to the master branch of Npgsql . With this merge, Npgsql has officially initial support for EF-6! How to compile For now, in order to compile Npgsql to use EF-6, you have to open the solution file NpgsqlEF6.sln. Later,  as suggested by Pēteris Ņikiforovs , the idea is that we create a new configuration inside main project solution instead of maintain 2 separated projects. Another thing you will need to compile Npgsql is the latest release of EntityFramework assembly through NuGet: PM> Install-Package EntityFramework -Pre That's it! Now you will be able to play with Npgsql and EF-6. Check out my previous post about how to use Npgsql with EntityFramework. I'd like to thank Pēteris Ņikiforovs for his patch. And maxbundchen for his patch about Open/Close events needed for EF-6. Please, give it a try and let me know ...
44 comments
Read more