MissingMethodException ConnectionString

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
Post Reply
David82
Posts: 4
Joined: Fri 03 Feb 2012 12:31

MissingMethodException ConnectionString

Post by David82 » Fri 03 Feb 2012 12:51

I've developeed a simple aplication using dotConnect for PostgreSQL 5.70 Mobile Trial with Visual Studio 2005 but I've a problem.

My code is the next:
string sbconn = "host=172.30.32.107;database=babylon;user id=openerp;Password=postgres;";
PgSqlConnection conector = new PgSqlConnection();
conector.ConnectionString = sbconn;
conector.Open();

I have also tried:
PgSqlConnection conector = new PgSqlConnection();
conector.UserId = "openerp";
conector.Password = "postgres";
conector.Host = "172.30.32.107";
conector.Port = int.Parse("5432");
conector.Database = "babylon";
conector.Open();

In both cases the error is the same: MissingMethodException. What could be the problem?

Regards!!

David82
Posts: 4
Joined: Fri 03 Feb 2012 12:31

Post by David82 » Tue 07 Feb 2012 08:20

Help me, please. I tried with the sample applications and the same thing happens to me.

David82
Posts: 4
Joined: Fri 03 Feb 2012 12:31

Post by David82 » Tue 07 Feb 2012 08:28

For what it's help I have installed the file Devart.Data.PostgreSql.dll in two places:
- C: \ Program Files \ Microsoft.NET \ SDK \ CompactFramework \ v3.5 \ WindowsCE

- C: \ Program Files \ Devart \ dotConnect Mobile \ Oracle \ CF35 \ Devart.Data.Oracle.dll

Pinturiccio
Devart Team
Posts: 2420
Joined: Wed 02 Nov 2011 09:44

Post by Pinturiccio » Tue 07 Feb 2012 15:04

We could not reproduce the issue. Could you please specify the following:
1. The call stack of the received exception;
2. Which .NET Compact Framework do you use Devart.Data.PostgreSql.dll for?
3. The version of .NET Compact Framework your application is compiled for?
4. Which .NET Compact Framework version is installed on your mobile device?
5. Which operating system do you use?
6. Test project will be appreciated.

David82
Posts: 4
Joined: Fri 03 Feb 2012 12:31

Post by David82 » Mon 13 Feb 2012 11:42

Problem solved. The mistake was that I was working with an incorrect version of Visual Studio. Thank you very much.

Post Reply