Hi Carlos,
if we're in huge changes in codebase, I think, there's some problem with
*.csproj files.
The FirebirdSql.Web.Providers.csproj is located on other place (level)
than FirebirdSql.Data.FirebirdClient.csproj . And also some same files
(with same I think with same purpose in project) are on different levels.
Same for FirebirdSql.Data.UnitTests.csproj .
I think, we should have:
\trunk\NETProvider\source\FirebirdSql\Data
\trunk\NETProvider\source\FirebirdSql\Web
\trunk\NETProvider\source\FirebirdSql\UnitTests
...
and nothing more in \trunk\NETProvider\source\FirebirdSql\.
This will also allow as to build Web Providers against latest
FirebirdClient clearly.
I also propose to move AssemblyInfo.cs files into Properties folder,
where they should be (my VS places these files into this folder by default).
What do you think? (maybe i forgot something)
As you feel, this is not ultimative description, but you propably
know/feel what I'm talking about.
This will also follows namespaces as well, so code will be nice structured.
If you have no objections, I propose to select one day. I'll fetch trunk
and in 1-2 hours I'll make moves and commits. Then everybody can fetch
new structure.
PS: I've tryied this (on a small model) on my local tree and the idea
seems to be good.
--
Jiri {x2} Cincura
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
