Re: [Firebird-net-provider] DDEX provider - support files and installation
On 12/24/07, Carlos Guzmán Álvarez <[EMAIL PROTECTED]> wrote: > The actual trunk sources have the changes take a look at it ( there are > changes in base classes and interfaces ) Damn, I must missed some commits. :) Merry Christmas. -- Jiri {x2} Cincura (Microsoft Student Partner) http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
Hello: > Sorry for late reply, mail stucked on the bottom. > Don't worry :) > Well I think we can use: > * separate place (branch or tag or folder) in SVN > * create conditional builds > > I don't know, what changed in SDK. If it's some extension, I propose > to use conditional builds. But if there're some working changes, the > separation would be IMO better. > The actual trunk sources have the changes take a look at it ( there are changes in base classes and interfaces ) -- Carlos Guzmán Álvarez Vigo-Spain Blog: http://carlosga.wordpress.com/ FirebirdClient : http://www.firebirdsql.org/ XMPP Client : http://code.google.com/p/xmppclient/ ohloh : http://www.ohloh.net/accounts/4138 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
On 11/27/07, Carlos Guzmán Álvarez <[EMAIL PROTECTED]> wrote: > I know it will work with VS 2008 :) but there are too many changes in > DDEX implementation in the VS 2008 SDK so i think we can do an specific > version for that, what do you think ?? Sorry for late reply, mail stucked on the bottom. Well I think we can use: * separate place (branch or tag or folder) in SVN * create conditional builds I don't know, what changed in SDK. If it's some extension, I propose to use conditional builds. But if there're some working changes, the separation would be IMO better. -- Jiri {x2} Cincura (Microsoft Student Partner) http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
Hello: > I've tested it under VS2008 Final and works fine. :D IMO we don't need > branching. > I know it will work with VS 2008 :) but there are too many changes in DDEX implementation in the VS 2008 SDK so i think we can do an specific version for that, what do you think ?? -- Carlos Guzmán Álvarez Vigo-Spain Blog: http://carlosga.wordpress.com/ FirebirdClient : http://www.firebirdsql.org/ XMPP Client : http://code.google.com/p/xmppclient/ ohloh : http://www.ohloh.net/accounts/4138 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
On 11/26/07, Carlos Guzmán Álvarez <[EMAIL PROTECTED]> wrote: > Hello: > > Sorry for the delay. > > You have done some modification in sources? > > > Not yet, i'm going to move current DDEX provider to branches today so we > can modify the devel one to match VS 2008 I've tested it under VS2008 Final and works fine. :D IMO we don't need branching. > We can modify both instalers to install in they own folder inside > %ProgramFiles%\FirebirdClient > > ADO.NET Provider will get installed on : > > %ProgramFiles%\FirebirdClient\ADONETProvider > > DDEX Provider will get installed on > > %ProgramFiles%\FirebirdClient\DDEXProvider > Looks fine. -- Jiri {x2} Cincura (Microsoft Student Partner) http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
Hello: Sorry for the delay. > You have done some modification in sources? > Not yet, i'm going to move current DDEX provider to branches today so we can modify the devel one to match VS 2008 > If you install FirebirdClient it's by default in > %ProgramFiles%\FirebirdClient. The if you wan to install DDEX, the > default parth is also %ProgramFiles%\FirebirdClient. But in DDEX > installation are some files with same name as in FirebirdClient > installation. So installer asks you, whether to rewrite i.e. > readme.txt or let there the old. Which can be little bit confusing. > We can modify both instalers to install in they own folder inside %ProgramFiles%\FirebirdClient ADO.NET Provider will get installed on : %ProgramFiles%\FirebirdClient\ADONETProvider DDEX Provider will get installed on %ProgramFiles%\FirebirdClient\DDEXProvider -- Carlos Guzmán Álvarez Vigo-Spain Blog: http://carlosga.wordpress.com/ FirebirdClient : http://www.firebirdsql.org/ XMPP Client : http://code.google.com/p/xmppclient/ ohloh : http://www.ohloh.net/accounts/4138 - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
On 11/22/07, Carlos <[EMAIL PROTECTED]> wrote: > Hello: > > > 1. What about adding this files into some folders (i.e. VS2005, VS2008 > > + xxbit systems). This will be more clear for people, isn't it? > > Looks fine to me but i should have a modified version of the DDEX > provider for VS2008, and it maybe better to put the actual version on > the svn branchs, and let the VS2008 version live in trunk. I have installed DDEX for VS2008 Beta 2 and VS2008 Professional Final. In my trunk I have modified reg files, just waiting for commit. You have done some modification in sources? > What can be nice is to create folders for the reg files. Will be done ASAP. > > 2. Do we really care about files for VS with SDK? I think, wa can add > > some template into some separate directory with some info. If > > developer is so experienced that has VS SDK (and know what's it) he's > > probably able to use DDEX and create appropriate decision what and how > > to install. > > I think yes, packageless support may cut some feature available with the SDK. > > > 2.1. BTW no matter wheter you have VS SDK you can use ...Less.reg, isn't it? > > Sure. But i think it's good to have the reg files for people that may > have the VS SDK installed yet. OK. > > 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. > > Huuu haven't understood this well :) If you install FirebirdClient it's by default in %ProgramFiles%\FirebirdClient. The if you wan to install DDEX, the default parth is also %ProgramFiles%\FirebirdClient. But in DDEX installation are some files with same name as in FirebirdClient installation. So installer asks you, whether to rewrite i.e. readme.txt or let there the old. Which can be little bit confusing. > > 3.1. Maybe we should review current install process of all components > > (and maybe build). If community is interested, I can provide some > > thoughts I've made (the build process we can discuss privately, > > Carlos, to not spam list). > > We can discuss that of course OK. -- Jiri {x2} Cincura (Microsoft Student Partner) http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
Hello: > 1. What about adding this files into some folders (i.e. VS2005, VS2008 > + xxbit systems). This will be more clear for people, isn't it? Looks fine to me but i should have a modified version of the DDEX provider for VS2008, and it maybe better to put the actual version on the svn branchs, and let the VS2008 version live in trunk. What can be nice is to create folders for the reg files. > 2. Do we really care about files for VS with SDK? I think, wa can add > some template into some separate directory with some info. If > developer is so experienced that has VS SDK (and know what's it) he's > probably able to use DDEX and create appropriate decision what and how > to install. I think yes, packageless support may cut some feature available with the SDK. > 2.1. BTW no matter wheter you have VS SDK you can use ...Less.reg, isn't it? Sure. But i think it's good to have the reg files for people that may have the VS SDK installed yet. > 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. Huuu haven't understood this well :) > 3.1. Maybe we should review current install process of all components > (and maybe build). If community is interested, I can provide some > thoughts I've made (the build process we can discuss privately, > Carlos, to not spam list). We can discuss that of course -- Carlos Guzmán Álvarez Vigo-Spain Blog: http://carlosga.wordpress.com/ FirebirdClient : http://www.firebirdsql.org/ XMPP Client : http://code.google.com/p/xmppclient/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
Hello: > Carlos, are you alive? :) Sure, busy but alive ;) > -- > Jiri {x2} Cincura (Microsoft Student Partner) > http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com > > - > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ > ___ > Firebird-net-provider mailing list > Firebird-net-provider@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/firebird-net-provider > -- Carlos Guzmán Álvarez Vigo-Spain Blog: http://carlosga.wordpress.com/ FirebirdClient : http://www.firebirdsql.org/ XMPP Client : http://code.google.com/p/xmppclient/ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
Carlos, are you alive? :) -- Jiri {x2} Cincura (Microsoft Student Partner) http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
On 11/19/07, André Knappstein, Controlling <[EMAIL PROTECTED]> wrote: > 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. During sunday I was thinking about this a little bit more. Maybe (not tested yet) it wouldn't be difficult to create small application, that will list GAC for assembly (version, signature, ...), dtect OS version and then ask for VS stuff and then generates right *.reg file. If this will be "10 lines" app. maybe we can create it. But just thinking loud. > 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. Yes I know. But IMO if you're able to read documentation, create some app. you're able to read readme file, do simple steps and (maybe) subscribe to list and ask about problems (or use private mail). And these steps should be as friendly as possible. > 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. Yes, if you have some BLL with objects and collections in app. the DDEX isn't required so much. But sometimes, the DDEX can help. OTOH without DDEX the provider for FB wil be working, will be good for application development, but there's a lost of people, that need/use DDEX (and maybe writing reviews for FB and Firebird's additional tools) so it's good, that we have it. > 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. Yes, exactly. So that, I'm thinking about simplyfing the installation (or better to say orientation in installation) as much as we can. Or maybe making it more developer friendly. -- Jiri {x2} Cincura (Microsoft Student Partner) http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
Re: [Firebird-net-provider] DDEX provider - support files and installation
> 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/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider
[Firebird-net-provider] DDEX provider - support files and installation
Hi Carlos and *, now we have bunch of *.reg files for importing stuff into registry when installing DDEX provider. I've now finished testing VS 2008 & DDEX and we will have another files. So wanna to ask: 1. What about adding this files into some folders (i.e. VS2005, VS2008 + xxbit systems). This will be more clear for people, isn't it? 2. Do we really care about files for VS with SDK? I think, wa can add some template into some separate directory with some info. If developer is so experienced that has VS SDK (and know what's it) he's probably able to use DDEX and create appropriate decision what and how to install. 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. 3.1. Maybe we should review current install process of all components (and maybe build). If community is interested, I can provide some thoughts I've made (the build process we can discuss privately, Carlos, to not spam list). JC -- Jiri {x2} Cincura (Microsoft Student Partner) http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Firebird-net-provider mailing list Firebird-net-provider@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/firebird-net-provider