Don't hold your breath. I've paid for another year of license fee back in November, because I just assumed that they must have already added support VS2022, like any other respectable component supplier did at the time.
They had access to betas, RCs, and other preview versions which they could've leveraged to ensure dotconnect's compatibility by the official launch. They just don't care about this products and their subscribers anymore.
Search found 36 matches
- Fri 18 Feb 2022 08:05
- Forum: Entity Developer
- Topic: Visual Studio 2022
- Replies: 29
- Views: 1083685
- Tue 30 Nov 2021 16:43
- Forum: Entity Developer
- Topic: Visual Studio 2022
- Replies: 29
- Views: 1083685
Re: Visual Studio 2022
I'm also waiting for VS2022 support as .NET 6.0 is incompatible with VS2019, so if I want to target the latest LTS, I'm forced to upgrade.
- Sat 12 Oct 2019 19:11
- Forum: dotConnect for PostgreSQL
- Topic: Bug in 7.14.1470 ?
- Replies: 5
- Views: 10501
Re: Bug in 7.14.1470 ?
I can confirm that the latest working version is 7.13.1437
- Sat 12 Oct 2019 18:55
- Forum: dotConnect for PostgreSQL
- Topic: Bug in 7.14.1470 ?
- Replies: 5
- Views: 10501
Re: Bug in 7.14.1470 ?
Same happened to me, I had to revert back to 7.13.1366.
- Thu 29 Mar 2018 10:58
- Forum: dotConnect for PostgreSQL
- Topic: DataSet manager won't open in VS2015
- Replies: 5
- Views: 9838
Re: DataSet manager won't open in VS2015
It's been a week and there is no fix yet
- Fri 23 Mar 2018 12:50
- Forum: dotConnect for PostgreSQL
- Topic: DataSet manager won't open in VS2015
- Replies: 5
- Views: 9838
Re: DataSet manager won't open in VS2015
Thanks. I'm really looking forward to download the fixed version.Pinturiccio wrote: ↑Fri 23 Mar 2018 11:13 We have reproduced the issue. And we have fixed the bug with throwing the "IDE not supported" exception by DataSet Manager in Visual Studio 2017 of versions 15.6.*. We will post here when the corresponding build of dotConnect for PostgreSQL is available for download.
- Thu 22 Mar 2018 14:06
- Forum: dotConnect for PostgreSQL
- Topic: DataSet manager won't open in VS2015
- Replies: 5
- Views: 9838
DataSet manager won't open in VS2015
I sent the support request below through the ticketing system two workdays ago but apparently Devart is not interested in supporting paying customers anymore.
Maybe someone else can help:
At this point any help is appreciated.
Maybe someone else can help:
Code: Select all
Product: dotConnect for PostgreSQL
Product Version: 7.10.1086.0
OS Version: Windows 10
Platform: x64
Is registered user: True
License number: xx
Details:
I'm using Visual Studio Community 2017 15.6.3. I'm unable to open DataSet manager on untyped datasets. I tried to right-click on the component then select Edit and also Tools/PostgreSQL/DataSet manager, but nothing happens.
I have tried reinstalling the component, didn't help. I suspect it has something to do with a recent VS update.
- Wed 26 Mar 2014 11:54
- Forum: dotConnect for PostgreSQL
- Topic: Connection resets on PgSqlAlerter.Start() without SSL options
- Replies: 5
- Views: 5766
Re: Connection resets on PgSqlAlerter.Start() without SSL options
Thanks. Will you fix this bug retrospectively in v5 as well?
- Wed 19 Mar 2014 23:35
- Forum: dotConnect for PostgreSQL
- Topic: Connection resets on PgSqlAlerter.Start() without SSL options
- Replies: 5
- Views: 5766
Connection resets on PgSqlAlerter.Start() without SSL options
I'm using dotConnect for PostgreSQL 5.0.449.0 with PostgreSQL server 9.1.
I have a PgSqlDataSet which connects to my server through a shared PgSqlConnection. This connection is shared with a PgSqlAlerter component. My alerter's list is preloaded during design time with a few alerts and another one is amended after the PgSqlConnection is successfully opened. The alerter is only started for the first time after this supplemental alert is added. This is where the unexpected behaviour occurs.
At this point dbMonitor show a new connection request with almost the same parameters, only SslOptions are not copied. This results in a fatal error since my server is configured to refuse non-SSL connections. Disabling connection pooling doesn't help, a new connection is opened anyways.
I have a PgSqlDataSet which connects to my server through a shared PgSqlConnection. This connection is shared with a PgSqlAlerter component. My alerter's list is preloaded during design time with a few alerts and another one is amended after the PgSqlConnection is successfully opened. The alerter is only started for the first time after this supplemental alert is added. This is where the unexpected behaviour occurs.
At this point dbMonitor show a new connection request with almost the same parameters, only SslOptions are not copied. This results in a fatal error since my server is configured to refuse non-SSL connections. Disabling connection pooling doesn't help, a new connection is opened anyways.
Code: Select all
2014.03.20. 0:26:27 n/a dotConnect for PostgreSQL monitoring is started Complete
2014.03.20. 0:26:27 0,717 Open connection: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Pooling=True;SSLMode=Allow;" Complete
2014.03.20. 0:26:27 0,000 Connect: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Pooling=True;SSLMode=Allow" Complete
2014.03.20. 0:26:28 0,031 Execute: SELECT version() Complete
2014.03.20. 0:26:28 0,016 Execute: show integer_datetimes Complete
2014.03.20. 0:26:28 0,015 Execute: show bytea_output Complete
2014.03.20. 0:26:28 0,016 Execute: SET autocommit=true Complete
2014.03.20. 0:26:28 0,015 Execute: SET datestyle=ISO ; SET client_encoding='UTF8' Complete
2014.03.20. 0:26:28 0,016 Execute: SELECT oid FROM pg_type WHERE typname like 'geometry' Complete
2014.03.20. 0:26:28 0,016 Prepare: SET ROLE Y Complete
2014.03.20. 0:26:28 0,015 Execute: SET ROLE Y Complete
(log entries omitted) -> application executes PgSqlAlerter.Start() here
2014.03.20. 0:26:36 0,000 Creating pool with connections string: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Pooling=True;SSLMode=Disable" Complete
2014.03.20. 0:26:36 0,000 Creating object Complete
2014.03.20. 0:26:36 0,000 Creating pool with connections string: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Connection Timeout=0;Pooling=True;SSLMode=Disable" Complete
2014.03.20. 0:26:36 0,000 Creating object Complete
2014.03.20. 0:26:36 n/a Open connection: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Connection Timeout=0;Pooling=True;SSLMode=Disable;" Pending
2014.03.20. 0:26:36 0,000 Connect: "User Id=Y;Password=X;Host=0.0.0.0;Database=Z;Unicode=True;Character Set=UTF8;Connection Timeout=0;Pooling=True;SSLMode=Disable" Complete
2014.03.20. 0:26:37 0,000 Disconnect Complete
- Wed 23 May 2012 14:34
- Forum: dotConnect for PostgreSQL
- Topic: Transactions with untyped dataset
- Replies: 6
- Views: 10019
Re: Transactions with untyped dataset
I was afraid of this. Thank you however!
- Wed 23 May 2012 08:51
- Forum: dotConnect for PostgreSQL
- Topic: Transactions with untyped dataset
- Replies: 6
- Views: 10019
Re: Transactions with untyped dataset
Could you provide an example how to do it?
- Sun 20 May 2012 20:54
- Forum: dotConnect for PostgreSQL
- Topic: Transactions with untyped dataset
- Replies: 6
- Views: 10019
Re: Transactions with untyped dataset
I've sent the requested files
- Thu 17 May 2012 21:50
- Forum: dotConnect for PostgreSQL
- Topic: Transactions with untyped dataset
- Replies: 6
- Views: 10019
Transactions with untyped dataset
I'm trying to post changes using an untyped dataset and a stored procedure in the same transaction using dotConnect Professional. The problem is that if posting dataset succeeds, but the stored procedure afterwards doesn't, rolling back the transaction doesn't roll back the dataset to its original state, the dataset looks like it has been successfully commited. Is there any solution to avoid this problem?
- Fri 23 Dec 2011 19:33
- Forum: dotConnect for PostgreSQL
- Topic: How to generate update command with PgSqlDataTable?
- Replies: 3
- Views: 5358
Ok, now I get what it's supposed to do. I actually want to build an update command, which only contains the changed field's definition. The point of doing this is that since postgres 9 it is possible to set column-level privileges, but if I use an update query which sets every field of the table, the whole thing becomes pointless.
Let's say there are 3 columns:
Is there any practice to circumvent this?
Thanks!
Let's say there are 3 columns:
- Column A
Column B
Column C
Is there any practice to circumvent this?
Thanks!
- Tue 20 Dec 2011 16:32
- Forum: dotConnect for PostgreSQL
- Topic: How to generate update command with PgSqlDataTable?
- Replies: 3
- Views: 5358
How to generate update command with PgSqlDataTable?
I'm wondering if it's possible to generate update and select commands with a PgSqlDataTable class? I've filled connection, columns, contraints, primary key, selectcommand, refreshingfields, refreshmode, updatingfields, updatingkeyfields and updatingtable.
Is there a member of PgSqlDataTable which generates the insertcommand and updatecommand for me? It would be nice to only update fields which have been modified before.
Is there a member of PgSqlDataTable which generates the insertcommand and updatecommand for me? It would be nice to only update fields which have been modified before.