Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Created attachment 308 [details]
example from Npgsql documentation
(sorry if wrong product/component but I'm unable to find out where to post bugs about Npgsql: I know that Sys.Data is not correct, where is the correct product?).
The Npgsql distributed with Mono seems outdated.
For example the attached source code is taken straight from Npgsql Documentation web site http://npgsql.projects.postgresql.org/docs/manual/UserManual.html (Working with Arrays) and does not even compile, giving the error:
prova.cs(20,75): error CS0117: `NpgsqlTypes.NpgsqlDbType' does not contain a definition for `Array'
/usr/lib/mono/gac/Npgsql/126.96.36.199__5d8b90d52f46fda7/Npgsql.dll (Location of the symbol related to previous error)
Compilation failed: 1 error(s), 0 warnings
Using the Npgsql-distributed binary (instead of the Mono integrated) everything works: compilation and execution.
There are even more issues about using Postgresql Enums or TimestampTZ... (but not with the Npgsql-distributed binary).
We stopped updating Npgsql looooong time ago. The version we ship is, AFAIK, just for backwards compatibility with some programs (?).
You should get Npgsql from http://npgsql.projects.postgresql.org/ and distribute the dll with your application.
> The version we ship is, AFAIK, just for backwards compatibility
> with some programs (?).
That is wrong reasoning.
See my reasoning in the bug