On 3/8/08, Daniel Rail <[EMAIL PROTECTED]> wrote:
> Jiri does recognize that the installation of the DDEX support would
> most likely be better automated via the installation.
Exactly. At least to provide some semi-automated steps and hints.
> But, the ADO.Net driver itself is not that complicated to install.
> Simply add it to the GAC, by using the .Net framework's gacutils.exe
> command line. Then, you can go in VS and add it to the toolbox, by
> choosing from the list of components available in the GAC. Or even
> simpler, skip the GAC registration and go straight into VS and go
> into the "Choose Toolbox Items" and "Browse" for the FirebirdClient
> dll, to add it to the VS Toolbox. And, then you can use the
> components for your projects. But, if you want more support within
> VS, then you have to install FirebirdClient's DDEX.
In fact, only issue related to installation, I see, is this:
1. Copy it to some place.
2. (Optional) Register it to GAC.
Nothing more. The DDEX has separate install, so that's all. And these
two steps can be done in simple batch file/console app.
--
Jiri {x2} Cincura (CTO x2develop)
http://blog.vyvojar.cz/jirka/ | http://www.ID3renamer.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Firebird-net-provider mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/firebird-net-provider