On 3/7/08, terrytornado [EMAIL PROTECTED] wrote:
It's a big problem to make a full install routine. ??
For GAC and registry it's only a small issue solvable with couple of
questions in batch file. But editing (and parsing) machine.config
files (32- and 64-bit) isn't easy (if we don't wanna to
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
Hi,
At Friday, March 07, 2008, 11:15 AM, terrytornado wrote:
Hi all,
i'm 15 years developing under Delphi. Now i try c# and new to Visual Studio.
I have big problems to install the firbird VS add in.
It's a big problem to make a full install routine. ??
Making addionally changes in
Hi all,
i'm 15 years developing under Delphi. Now i try c# and new to Visual Studio.
I have big problems to install the firbird VS add in.
It's a big problem to make a full install routine. ??
Making addionally changes in certain files per hand it's not the best way.
Too many failures can
Today, during msi installation building, I was wondering, whether
FirebirdClient needs installation. From my POV it's mainly for
developers, so, I hope, they are able to download some archive unpack
and add it to right place, isn't it? (In fact it can be easier to do
this with non-installation
Jiri,
While I agree that most developers have the capability to unpack and add the
elements to the correct place, it is an area that prone to error. One of
the things a computer is good at is doing tedious things correctly once it
has been trained (programmed). To me, it makes more sense to
Hi,
At Thursday, March 06, 2008, 11:22 AM, Marvin Cook wrote:
Jiri,
While I agree that most developers have the capability to unpack and add the
elements to the correct place, it is an area that prone to error. One of
the things a computer is good at is doing tedious things correctly once
