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

UUID datatype and COPY IN/OUT support added to cvs

Hi all! It was just added support to uuid datatype in cvs head. This type will be available in next Postgresql release 8.3. Thanks to David Bachmann for his patch! You can get more info about this patch in this mailing list post . Also was added support for copy in and copy out operations. Now, users can provide streams which can be copied directly to and from Postgresql tables! Thanks to Kalle Hallivuori for providing a patch! Thanks to Truviso for giving support to Kalle. More info about that including a demo and ready to use compiled Npgsql.dll versions can be found here . That's it! As soon as we get more features added, I will post info about them here. Stay tuned! :)
1 comment
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

Using Entity Framework 6 with Npgsql 2.1.0

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