Thanks for confirming. So to clarify on the 3rd point, I mean to use v1.7
of the provider. I already have v2.0 installed and integrated using the
Simpson approach. I was considering going back to try using the 1.7
version.
""Carlos Guzmán Álvarez"" <[EMAIL PROTECTED]> wrote in message
news:
Hello:
Is it possible to integrate the Firebird .NET 1.7 Provider with DDEX?
No.
It is
my understanding that non compliant .NET 2.0 Providers do not take advantage
of the VS DDEX.
Correct.
Therefore all I have to do is install the executable, and
place the assembly references in my web.co
Is it possible to integrate the Firebird .NET 1.7 Provider with DDEX? It is
my understanding that non compliant .NET 2.0 Providers do not take advantage
of the VS DDEX. Therefore all I have to do is install the executable, and
place the assembly references in my web.config file. Is this corre
Hello:
One other thing ... if you go packageless, you don't need the VSIP SDK
either. That and supporting all the Express Editions are the primary reason
I'm leaving the SQLite provider packageless.
Thanks !!! I will see if i can get some time next week ( after Tuesday
that is when finishes
""Robert Simpson"" <[EMAIL PROTECTED]> wrote:
> Perhaps I might be able to lend a little help on the DDEX front ...
>
:)
You did it!
Thanks
Juan Jose
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that
One other thing ... if you go packageless, you don't need the VSIP SDK
either. That and supporting all the Express Editions are the primary reason
I'm leaving the SQLite provider packageless.
Robert
---
This SF.Net email is sponsored by x
Perhaps I might be able to lend a little help on the DDEX front ...
Here's a few changes to the reg file that should make Firebird packageless.
Replace any occurrance of "VisualStudio" with "VWDExpress" to make the reg
file work on that Express edition:
- Cut Here -
ÿþWindows Registry
