Commented by: Mercea Paul (paul.mercea)

I confirm this with VS 2013 .
I need to install DDEX again after each extension update.
Project are compiling but get error when i try to open entity data model or dataset ... after reinstalling is working again.

Commented by: André Ziegler (andre.ziegler)

thanks for the confirmation, that it also happens under VS2013.

Commented by: Roger Mandisa (rogerman)

even I can't get the connectionstring after reinstall VS2013, NETProvider and DDEX

Commented by: Mercea Paul (paul.mercea)

Roger Mandisa, I'm in the same situation, everything working great except DDEX for Firebird.
I cannot believe is related to the fact that is targeted to .Net Framework 2.0 .....

Commented by: André Ziegler (andre.ziegler)

you both may run into this issue:

DNET560

remove the older Firebird Provider entry from the config file

Commented by: Don VonderBurg (dvonderburg)

This still happens on 4.6.1.0 During code changes in datasets the DDEX will lose the object and throw errors in the Visual Studio 2013 environment.

Steps I use to recover.

1. Uninstall DDEX 3.0.1
2. Uninstall Client 4.6.1.0
3. Using nuget remove all Firebird client from solution.
4. Install Client 4.6.1.0
5. Install DDEX 3.0.1
6. Edit machine.config and remove extra Firebird reference.
7. Install nuget for Firebird client to solution.

Then my environment will work for a while until some action to dataset will trigger the disconnect error messages again. I have not found the action that causes the loss of the object.

Commented by: André Ziegler (andre.ziegler)

any progress about this?

Commented by: André Ziegler (andre.ziegler)

ok, I did some search and tried the DDEX provider for PostgreSQL. After updating an extension the PostgreSQL provider is still shown.

I looked at the code:

https://github.com/npgsql/npgsql/tree/develop/src/NpgsqlDdexProvider

and I see that DDEX provider comes as a VSIX format.

It implements RegistrationAttribute with Register and Unregister methodes.

https://msdn.microsoft.com/en-us/library/microsoft.visualstudio.shell.registrationattribute.aspx

Seams like this cause that other providers are still registered while your direct registry way removes the DDEX provider after an extension update.

So can you please also implement the DDEX provider as VS extension (VSIX)?

Commented by: @cincuranet

Replaced by DNET659.