SCM

[#1000461] Rename the assemblies...

View Trackers | Feature Requests | Download .csv | Monitor

Date:
2005-12-01 16:05
Priority:
3
State:
Closed
Submitted by:
Nobody
Assigned to:
Nobody (None)
Category:
None
Group:
None
Resolution:
None
 
Summary:
Rename the assemblies...

Detailed description
1- i agree with merging Npgsql and the MonoSecurity assembly into one single assembly can be fine

2- some names can be renamed as follows
Npgsql.dll -> PostgreSQL.dll
using Npgsql; -> using PostgreSQL;
NpgsqlDbType.XXX -> PgDbType.XXX
NpgsqlConnection -> PgConnection
...

3- support for dotnet 2.0

4- PostgreSQL known with better documentation i think Npgsql can have better documentation.

5- i think a gui can be writen with dotnet and Npgsql (like PgAdmin)

6- can Npgsql have multiple solution files for Visual Studio , SharpDevelop , Nant, Nmake...

7- NpgsqlDbType namespace can be merge with Npgsql namespace

8- a server explorer addin for designing within visual studio

9- and can BSD license

Thanks...

Followup

Message
Date: 2013-12-12 23:09
Sender: Shay Rojansky

1. For release 2.2, we plan to examine whether Mono.Security is still needed at all.
2. Name changes will break compatibility and should be avoided
3. This is done, we ship a DLL targeting.NET 2.0
4. Working on it... Checkout the new wiki at https://github.com/npgsql/Npgsql/wiki
5. That's out of scope for this project, there are many Postgresql GUIs out there
6. We recently added multiple SLNs. No support for nant/nmake is planned
7. Agreed in principle, but would again break compatibility
8. DDEX work is being worked on at the moment
9. Npgsql is licensed under the Postgres license

Attached Files:

Changes:

Field Old Value Date By
status_idOpen2013-12-12 23:09roji
close_dateNone2013-12-12 23:09roji
Powered By FusionForge