Trial and Pro 2.80 DbExplorer VS.NET Integration Problem

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
dbssoft
Posts: 5
Joined: Tue 28 Jun 2005 17:41

Trial and Pro 2.80 DbExplorer VS.NET Integration Problem

Post by dbssoft » Tue 28 Jun 2005 17:50

Hi Everyone,

Using both MySQLDirect .NET 2.80 trial and pro licensed versions, DbExplorer does not open in VS.NET 1.1 IDE.

Interestingly, I can open *.qry files without issue and the Data Window and Create… toolbar buttons function as expected.

I’m wondering if the panel does indeed display, but is not viewable (for some yet to be known reason) even when all other panes are closed.

Uninstalls and reinstalls (with reboots in between...just for grins) does not seem to be the solution in this case.

I am unable to find anything related to this issue in the forum, and on google.

(1) Is there a set of manual steps that you can suggest to make sure all config information is removed during the uninstall?

(2) Do you have any advice as to how best to resolve this issue? I hope to avoid reinstalling VS.NET.

XP Pro SP 2
VS.NET IDE 7.1.3088
.NET 1.1.4322 SP1
MySQLDirect .NET 2.80.7
Tools 1.20.1.0


Thank you for your time,
DBS

dbssoft
Posts: 5
Joined: Tue 28 Jun 2005 17:41

Post by dbssoft » Tue 28 Jun 2005 19:02

FYI UPDATE:

Behavior appears to be related somehow to the Windows User environment.

Created new windows user "John Smith".
Logged in as John.
Opened VS.NET.
Opened DbExplorer.
All's well.

Logged back in as "DBS".
Still broken. :(

dbssoft
Posts: 5
Joined: Tue 28 Jun 2005 17:41

Post by dbssoft » Tue 28 Jun 2005 19:49

FYI UPDATE:

Deleted DBS's [HKEY_CU]\Software\Microsoft\VisualStudio\7.1 registry tree. Replaced with John's.
Deleted DBS's [D&S\DBS]\Application Data\Microsoft\VisualStudio folder. Replaced with John's.

Still broken. :(

dbssoft
Posts: 5
Joined: Tue 28 Jun 2005 17:41

Post by dbssoft » Tue 28 Jun 2005 20:24

SOLVED:

Simple.

(1) Uninstalled MySQLDirect .NET 2.80 Pro
(2) Removed all Core Lab artifacts from Software registry tree
(3) Removed all Core Lab artifacts from Applicaton Data folder
(4) Reinstall

Apparently, some stale config info was not uninstalled during the uninstall.

PITB

Duke
Devart Team
Posts: 476
Joined: Fri 29 Oct 2004 09:25

Post by Duke » Wed 29 Jun 2005 07:43

We'll check our installation.

Post Reply