> 2.1. BTW no matter wheter you have VS SDK you can use ...Less.reg, isn't it?
> 3. What about installation. Maybe should provide some no so common > path like %ProgramFiles%\FirebirdClient, 'cause there're *.txt files > with same name from FirebirdClient installation, so during install > some can be confused. I know, it's not a big deal, bug it's also small > change. Jiri, all of that sounds VERY good to me. If the time for implementing these changes can be spared this will be a big help for a lot of people. About "developers" and their abilities: the world is not just black and white but has a lot of shades between. I would not call myself a "real" developer and especially I do not have time to learn about all new things at once. But I wrote quite a big application, now half based on Firebird and already 5% written in C#. And the income of about 50 employees depends on that. So I am also a bit more than a hobbyist. I always demonstrate in my workshops how to use ODBC in the beginning, and once the attendees understood ADO.net principles, they do not need DDEX anyway. But those who do not listen to me are already re-converting their just converted-to-Firebird applications over to MSSQL just because it's too complicated to install the designtime support for the FB provider. Thanks, André ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
