DDEX not installing with package.
GirusVirus opened this issue · 10 comments
After installing the github package, I was able to successfully access the db. However the I was not able to create a data connection as the ADO support was not installed in the DDEX for VS 2019
The ADO driver is a separate install. The readme for the DDEX driver recommends using the installer to install it. The ADO.NET driver installer properly sets up the machine.config changes outlined in the readme for you.
Look at the releases https://github.com/Embarcadero/IB.NETDataProvider/releases/tag/v7.10.2 There are two msi installers, one for the ADO driver and one for the DDEX driver. The DDEX has manual steps to get installed into VS 2019, look at the docx included in both installers or as a separate download in the releases for detailed instructions on installing the DDEX driver into VS itself.
Hi Jeff, thank you I got it to work and I was able to create a connection. Now the only issue I have is that every time I update VS2019, the private registry reverts back and erases the edits. Is there a way to make the changes persistent?
Unfortunately, no. The same issue was reported on the Firebird DDEX forums that this one is highly based on. I found that annoying myself during development and testing.
Glad it is working for you now. The installers make it much easier to have everything in its right place and the right config files updated. Unfortunately once Visual Studio went to private registries as of VS 2017 the whole DDEX automatic installer becomes impossible.
Jeff, that is what I thought. However, it is possible as IBProvider was able to do it. I have been using IBProvider for some time and it seems to be able to keep the configuration alive after updates. He might be implementing a different tech, as those ADO.NET drivers and also connects to system global OLE DB, which can be used from excel, and other applications that support OLE DB. Thanks.
I found that the DDEX changes in Microsoft's docs is spread out and not that easy to follow. If you run across anything on this subject add a link in this comment chain and I'll see it and investigate further. Just figuring out where all the pieces went (machine.config, etc) was troublesome.
Thank you, will do.
The IBProvider is installing it through VSIX. The code we based the IB DDEX on is the older style installation. That is probably the difference and why it gets lost after updates.