VS 2005 July CTP and 'CoreLab.PostgreSql load error

Traveler · Post by **Traveler** » Sat 23 Jul 2005 22:57

I'm getting the following exception:

[TypeLoadException: Declaration referenced in a method implementation cannot be a final method. Type: 'CoreLab.Common.DbDataReaderBase'. Assembly: 'CoreLab.PostgreSql, Version=2.11.8.0, Culture=neutral, PublicKeyToken=09af7300eec23701'.]
CoreLab.PostgreSql.m.h() +0
CoreLab.PostgreSql.m.b() +204
CoreLab.Common.DbConnectionFactory.a(DbConnectionBase A_0) +179
CoreLab.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection) +165
CoreLab.PostgreSql.PgSqlConnection.Open() +45

A searched the Web a bit, and came up with the following:

"After some more looking I've tied this problem to overrides of the Dispose
method. The error doesn't occur in the dispose method itself but, get this,
at the call to a function which refers to a form that has an overridden
dispose method...
Microsoft and Don Box recommend that you avoid using dispose to clean up
module/class level objects and it would seem that this is especiallly sound
advise."

Yuri · Post by **Yuri** » Mon 25 Jul 2005 13:00

We got your request and now examines the problem.
Unfortunately now we couldn't give you any information.
As soon as we solve the problem, we'll let you know.

Yuri · Post by **Yuri** » Tue 26 Jul 2005 11:27

This problem happens if you are trying to use data provider for .NET Framework 1.
To use the data provider with .NET Framework 2 you have to install pgsqlnet211std2.msi (standard edition) or pgsqlnet2.msi (trial edition).

Traveler · Post by **Traveler** » Wed 27 Jul 2005 06:33

Of course I installed pgsqlnet211std2.msi. On fresh Windows XP with fresh Visual Studio 2005 July CTP that was released about three weeks ago.

The files are in C:\Program Files\Corelab\PostgreSQLDirect.NET2, which seems to indicate that this is the provider for .NET 2, right?

There is a weird thing though: CSharp.sln in C:\Program Files\Corelab\PostgreSQLDirect.NET2\Samples says its version is "Visual Studio 2002" and that it was modified 5/10/2005.

Are you sure everything is OK with that build?

Yuri · Post by **Yuri** » Wed 27 Jul 2005 07:36

We tested the Data Provider and samples with MS Visual Studio 2005 8.0.50215.44 and all works fine.

Guest · Post by **Guest** » Wed 03 Aug 2005 06:43

I'm disappointed to see that the PosgreSQLDirect.NET 2.11.9.0 still doesn't work with MS Visual Studio 8.0.50630.0 while the open source Npgsql works just fine.

This is not acceptable. I swear to God if the situation is not changed two weeks from now, we'll switch to Npgsql and will never look back.

Yuri · Post by **Yuri** » Wed 03 Aug 2005 09:12

The problem is in that .NET Framework v2.0.50215 is not compatible with v2.0.50630. We are not able to make builds for each beta version of .NET Framework.
When .NET Framework v2 releases we will certainly support it.

Traveler · Post by **Traveler** » Tue 23 Aug 2005 04:32

"We are not able to make builds for each beta version of .NET Framework"

Why not? New VS 2005 betas are coming out once in a quarter - a rather slow-moving target. How come that Npgsql - which is open source - works fine with the latest VS 2005 release?

Besides, v2.0.50630 is a version very close to a release candidate. Visual Studio 8.0.50630.0 no longer has "Beta" in its logo.

Anyway, since you refused to support the VS 8.0.50630.0 that fixes a number of crucial bugs present in Beta 2, I have no other option but to switch back to Npgsql. Waiting till November when the VS 2005 is going to be officially released is not acceptable.

Guest · Post by **Guest** » Thu 15 Sep 2005 03:17

We tried using your latest .Net 2.0 PostGreSQL DLL with the August CTP of Visual Studio 2005 and still get the same problem.

With the recurring delays in your fixes and support uncertainties, it's becoming very difficult to convince management about the viability of your driver.

There is still a window of opportunity but it's going to be very close - better communication and timeframes are of utmost importance.

Guest · Post by **Guest** » Thu 06 Oct 2005 14:24

I am getting the same error since I upgraded to the release candidate of VS 2005. This has effectivly halted all development on this application. I read the earlier postsa bout not being able to compile for each new release, but I really need this one and need it ASAP. The descision was made to develop this new application in the new VS so that we would not have to re-write it later. I can not halt my development now because you do not wish to recompile your code to support us. All of the other custom control providers have release working versions for the latest Release Candidate. I need you to re-think your position on this one. Please let me knwo what your intentions are. I can not hold off development until November, that is just not going to happen, and I would hate to have to start over with someone else, but I will if forced to.

Please advise us all as to if you are going to help us out since I am sure I am not the only one in this position.

SecureGen · Post by **SecureGen** » Thu 06 Oct 2005 15:03

You can use version of PostgreSQLDirect .NET 2.20 provider for .NET1 framework in your .NET2 projects as it was described in http://crlab.com/forums/viewtopic.php?t=2013.
If you have any problem using this version, please let us know.

Guest · Post by **Guest** » Wed 09 Nov 2005 14:54

we are in mid of development cycle, this problem should NEVER occur. This hit us at a very critical time, if we have to upgrade, its going to be to kick corelabs out of our source.

SecureGen · Post by **SecureGen** » Thu 10 Nov 2005 09:47

We plan to release next build of PostgreSQLDirect .NET that supports .NET2 framework and VS2005 during next week.

Ron Barlean · Post by **Ron Barlean** » Fri 18 Nov 2005 01:35

I followed the dialog and I am wondering if it has been resolved yet?

Devart Forums