Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 10 of 10 total
Thread ElevateDb data connection provider stopped working in VS2008
Tue, Sep 16 2008 9:08 AMPermanent Link

Darren McBride
Hi,

I am currently evaluating the ElevateDb product as our database of choice for non-server based databases (i.e. to replace Access/Foxpro and the
like). Everything has been going well, but today a data connection that I had already configured in Visual Studio has stopped working and gives me
the following error message:

Could not load file or assembly 'elevate.elevatedb.data, Version=2.1.4.0, Culture=neutral, PublicKeyToken=cf9bc1202c75e9e2' or one of its
dependencies. The system cannot find the file specified.

I have checked the DLL's and they are in the correct location. I have checked the machine.config file and it is pointing to the correct version of the
DLL's. I have checked the registry settings for data connections in Visual Studio 2008 and they all appear fine. I have reinstalled ElevateDb and
this has not worked. I have restarted my PC and again the problem persists.

I can no longer configure any further data connections, either using ElevateDb or otherwise, as I keep receiving this message as soon as I try to
add a data connection.

Please help.

Thanks,
Darren
Tue, Sep 16 2008 9:16 AMPermanent Link

Darren McBride
All,

I have just added the 'elevate.elevatedb.visualstudio.dll' and 'elevate.elevatedb.data.dll' assemblies into the GAC and the data connection issue
does not occur.

Now however, instead of being presented with the detailed breakdown of properties available to create a connection string, I simply get a single
'ConnectionString' property.

Anyone any ideas ?

Thanks,
Darren
Tue, Sep 16 2008 10:16 AMPermanent Link

Darren McBride
All,

Sorry, just an additional note to say that I have checked two other posts in this group with similar issues, pertaining to the incorrect setup of the
DLL's in the machine.config file (i.e. pointing to the CF version instead of the VS version). I have checked these settings and all appear correct. I
have also checked the registry and it is also configured correctly.

I am using version 2.1.4 of the assemblies.

Thanks,
Darren
Tue, Sep 16 2008 10:36 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Darren,

<< Sorry, just an additional note to say that I have checked two other posts
in this group with similar issues, pertaining to the incorrect setup of the
DLL's in the machine.config file (i.e. pointing to the CF version instead of
the VS version). I have checked these settings and all appear correct. I
have also checked the registry and it is also configured correctly.

I am using version 2.1.4 of the assemblies. >>

Okay, first of all, something must have changed in either your project or
the machine.config in order to cause the data provider to not work with your
project anymore.  What you're seeing is a basic assembly version mismatch
issue, and the solution is to make sure that your project is trying to load
the proper version of the assembly, and that the machine.config file is
configured to ensure that the proper assembly is being found.  The issue of
only seeing the ConnectionString property in the Connection String Builder
is a symptom of the VS plugin assembly not being found and loaded properly.

If you could email me (timyoung@elevatesoft.com) your machine.config along
with your project, I can tell you where the issue is.

--
Tim Young
Elevate Software
www.elevatesoft.com

Tue, Sep 16 2008 11:59 AMPermanent Link

Darren McBride
Tim,

Thanks for the prompt response. I can mail you the project file, but the issue still happens when I have no solution open.

Here is the excerpt from my config file:

   <runtime>
      <assemblyBinding>
         <dependentAssembly>
            <assemblyIdentity name="Elevate.ElevateDB.Data" publicKeyToken="cf9bc1202c75e9e2"/>
            <codeBase version="2.1.4.0" href="file:///C:\Program
Files\ElevateDB\assemblies\edbprovider\Elevate.ElevateDB.Data.dll"/>
         </dependentAssembly>
         <dependentAssembly>
            <assemblyIdentity name="Elevate.ElevateDB.VisualStudio" publicKeyToken="009e2f3c00f33fa3"/>
            <codeBase version="2.1.4.0" href="file:///C:\Program
Files\ElevateDB\assemblies\edbprovidervs\Elevate.ElevateDB.VisualStudio.dll"/>
         </dependentAssembly>
      </assemblyBinding>
   </runtime>

It's certainly puzzling as it just stopped working when I booted up this morning. You are probably right about the conflict with another assembly,
but I can't see how VS2008 is picking one of them up. I have even changed my 2008 settings so that no project is loaded when the environment
starts, but still no luck.

Thanks,
Darren
Tue, Sep 16 2008 8:44 PMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Darren,

<< Here is the excerpt from my config file: >>

That looks fine.

<< It's certainly puzzling as it just stopped working when I booted up this
morning. You are probably right about the conflict with another assembly,
but I can't see how VS2008 is picking one of them up. I have even changed my
2008 settings so that no project is loaded when the environment starts, but
still no luck. >>

Did you do a search of your hard drive for any Elevate*.dll files ?  And did
you verify that you don't have any local copies of the ElevateDB assemblies
in any of your project directories (CopyLocal=True for the reference in the
project) ?

Thanks,

--
Tim Young
Elevate Software
www.elevatesoft.com

Wed, Sep 17 2008 11:57 AMPermanent Link

Darren McBride
Tim,

<<Did you do a search of your hard drive for any Elevate*.dll files ?  And did
you verify that you don't have any local copies of the ElevateDB assemblies
in any of your project directories (CopyLocal=True for the reference in the
project) ?>>

I did a full search and, as you rightly point out, had CopyLocal=True on two projects. I have since removed this setting, removed the extra DLL
files and searched the disk. I can confirm that the DLL's only exist now in the ElevateDb directory.

Unfortunately I am still getting only a connection string edit box in the data provider in VS2008.

Should I reinstall in an attempt to reset the environment ?

Thanks,
Darren
Thu, Sep 18 2008 5:34 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Darren,

<< Unfortunately I am still getting only a connection string edit box in the
data provider in VS2008.

Should I reinstall in an attempt to reset the environment ? >>

That will probably be the quickest solution.  Make sure that all EDB
assemblies are removed from the GAC, and then uninstall 2.01 B4.  Then you
can re-install it and you should be all set.  If you're still having issues,
then please let me know.

Did you figure out what changed on your machine to cause this ?  This type
of configuration doesn't just stop working without something interfering
with it.

--
Tim Young
Elevate Software
www.elevatesoft.com

Fri, Sep 19 2008 5:52 PMPermanent Link

Darren McBride
Tim,

I haven't tried this yet, but will report back when I try it in the next day or so.

I also haven't a clue what could have changed, as it literally happened overnight, and the only thing I had done was to build and run a project from
within VS2008 which I had previously built and run with no adverse effects on the provider.

Thanks,
Darren
Sat, Sep 20 2008 8:23 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Darren,

<< I haven't tried this yet, but will report back when I try it in the next
day or so. >>

No problem.  Just let me know if you're still experiencing problems, and we
can arrange to go more in-depth if you want.  I commonly do a remote desktop
log-in to examine the situation.

<< I also haven't a clue what could have changed, as it literally happened
overnight, and the only thing I had done was to build and run a project from
within VS2008 which I had previously built and run with no adverse effects
on the provider. >>

Hmm, I guess we'll just have to chalk it up to gremlins. Smiley

--
Tim Young
Elevate Software
www.elevatesoft.com

Image