Skip to main content

Where is vs.net design time support?


You may already know that VS.Net design time support has started a long time ago and didn't have too much support since then. 

Now that Npgsql release 2.0.12 is out, I want to put more attention to finish a version which adds design time support. I noticed that this is the biggest missing feature in Npgsql and I want to fix that. Npgsql users deserve to be able to use VS.Net design time support to help them create better apps which access Postgresql databases.

Although I can't give any concrete timeframe of when it will be available, I want you to know that I'm focused on this feature and it is not stalled. I hope to be able to give you more information soon.

Stay tuned.




Labels:

Comments

jmunin said…
We were expectantly waiting for news.
thank you for your excellent work.
10 October, 2012 13:38
Francisco Junior said…
Thanks for your words, jmunin. They are very rewarding. I hope to get vs.net support working soon.
11 October, 2012 12:46
Unknown said…
I would like to try how Npgsql work in some "real situation" and maybe I can switch from ODBC system to Npgsql. For start I see that Npgsql is a bit slower than native windows data system .

HVAC tec training in alaska
23 February, 2013 16:47
conan said…
In Bezug auf seine Liebe zu Uhren erklärte Gillespie: "Ich bin ein großer Typ für Werkzeuguhren. Ich habe eine anständige Sammlung von Uhren,replica uhren die für mich die Idee verkörpern, zu vereinfachen und zu perfektionieren." Ich glaube, ich habe mich immer für diesen Uhrenstil interessiert, weil er zu meinem Kochstil passt.rolex replica Leute, die es nicht besser wissen, finden es vielleicht einfach, aber für den Gelehrten ist klar, dass es darum geht, sich auf eine zu konzentrieren Ich liebe das Fehlen von Komplikationen auf dem Zifferblatt und wie zurückhaltend es ist.fake rolex Für mich machen Tudor und Panerai das besser als jeder andere. "
25 May, 2020 22:51
Post a Comment

Popular posts from this blog

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

Fixed! LOG: unexpected EOF on client connection

Hi all! Since we implemented connection pool in Npgsql, we received some complaints about EOF log messages being generated on Postgresql logs when using Npgsql. This was caused by Npgsql not sending the proper terminate message to Postgresql on pooled connections when the application terminated or more specifically when the assembly was unloaded. This is a long time problem with Npgsql connection pool. I even talked about it in the past . Up to now, I had no idea about how to fix that as I wasn't able to close the connections in the pool. When I tried to put a finalizer in NpgsqlConnectorPool, which would be triggered when the assembly was unloaded, I received object already disposed exceptions when trying to send something to the stream. That's when I came up with the "excellent" idea of subclassing the networkstream class and override its Dispose method so that I could send the postgresql terminate message before it was disposed! :) It worked like a charm! ...
5 comments
Read more

Npgsql 2.2.0 final release is out!

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. E...
15 comments
Read more