Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DDEX provider is lost after updating an extension in VS2012 [DNET581] #550

Closed
firebird-issue-importer opened this issue Dec 8, 2014 · 12 comments

Comments

@firebird-issue-importer
Copy link

@firebird-issue-importer firebird-issue-importer commented Dec 8, 2014

Submitted by: André Ziegler (andre.ziegler)

Is replaced by DNET659

Votes: 1

When I install an update to extension in VS2012 the DDEX provider is lost:

https://entityframework.codeplex.com/discussions/571855

Using ProcessMonitor I see that the VS writes NEW keys (REG_CREATED_NEW_KEY) under

HKCU\Software\Microsoft\VisualStudio\11.0_Config\DataProviders

for OleDb, SQLServer, Oracle, SQLCe, but I can't see Firebird. Why does this happen?

I have to run the setup again and repair the DDEX provider every time this happens again.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 8, 2014

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.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 8, 2014

Commented by: André Ziegler (andre.ziegler)

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 8, 2014

Modified by: André Ziegler (andre.ziegler)

description: When I install an update to extension in VS2012 the DDEX provider is lost:

https://entityframework.codeplex.com/discussions/571855

Using ProcessMonitor I see that the VS writes NEW keys (REG_CREATED_NEW_KEY) under

HKCU\Software\Microsoft\VisualStudio\11.0_Config\DataProviders

for OleDb, SQLServer, Oracle, SQLCe, but I can't see Firebird. Why does this happen? I have to run the setup again and repair the DDEX provider everything this happens again.

=>

When I install an update to extension in VS2012 the DDEX provider is lost:

https://entityframework.codeplex.com/discussions/571855

Using ProcessMonitor I see that the VS writes NEW keys (REG_CREATED_NEW_KEY) under

HKCU\Software\Microsoft\VisualStudio\11.0_Config\DataProviders

for OleDb, SQLServer, Oracle, SQLCe, but I can't see Firebird. Why does this happen?

I have to run the setup again and repair the DDEX provider every time this happens again.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 10, 2014

Commented by: Roger Mandisa (rogerman)

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

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 11, 2014

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 .....

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 12, 2014

Commented by: André Ziegler (andre.ziegler)

you both may run into this issue:

DNET560

remove the older Firebird Provider entry from the config file

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Feb 8, 2015

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.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 28, 2015

Commented by: André Ziegler (andre.ziegler)

any progress about this?

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Dec 28, 2015

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)?

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 1, 2019

Modified by: @cincuranet

Link: This issue is replaced by DNET659 [ DNET659 ]

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 1, 2019

Commented by: @cincuranet

Replaced by DNET659.

@firebird-issue-importer
Copy link
Author

@firebird-issue-importer firebird-issue-importer commented Aug 1, 2019

Modified by: @cincuranet

status: Open [ 1 ] => Closed [ 6 ]

resolution: Won't Fix [ 2 ]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants