Devart Forums

Hi,

In my project I'm using entitiy developer, dotconnect for sqlite.
and inside visual studio 2010 express all is doing well.
the project is being compiled and run fine.

after uploading the project's files to the hosting server,
I'm receiving the following message:

Could not load file or assembly 'Devart.Data.Linq, Version=3.0.10.0, Culture=neutral, PublicKeyToken=09af7300eec23701' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

the devart.data.linq version I'm using is: 3.0.16.0 taken from the devart/linq folder. how come on my machine all is good but on the remote server things are going wrong?

from some reason, something is looking for a lower version of that dll which does not exist.

does someone knows what's going on?

Shahar Weinstein

Most probably, the problem is that you refer to the particular (3.0.10) version of Devart.Data.Linq in your project. Please check the 'Specific Version' property of assembly references and, if the project is a web one, the entries referring to Devart.Data.Linq in the web.config files. When being uploaded to the deployment server, the application can not find the 3.0.10 version as only the 3.0.16 one is available.

The reason why these same references work well on your development machine is that the LinqConnect installation package includes the policy files that redirect the references from the assemblies of LinqConnect 3.0.10 to the ones of LinqConnect 3.0.16 (check the policy.*.Devart.* files in the GAC).

Please tell us if this helps.

hi

what you wrote sounds good but when i check my enviroment I cannot find any direction for a solution.
in my webconfig I've defined only this line:
so only the actual dlls will be loaded.
in the GAV I could find the policy files that are version 3.0.16.0. I didnt find other version.
from what I understand the project should work even on a remote machine depending only the dlls inside the BIN folder.
if something is looking for a lower version of dlls, it means something is wrong in one of the dlls I'm using and I'm supposed to use an older version of the devart.data.linq dll.

the bottom line ,is that I didnt find anything that put some light for me.
or understood clearly what I'm supposed to do.

Shahar.

is there anything I might need to update in the web.config file ?
I cannot install linq connect on the remote machine

Shahar.

does anyone can help me with this please?
my project is loosing time, and I've actualy started replacing all the
Devart code lines with the regular SQLlite code, because I need to finish with
this project today.

I've tried to upload the project files to two different hosting servers.
and got the same error on both. I realy want using your technology.

please help.
Shahar Weinstein.

Provided that the Devart assemblies are not mentioned in the web.config file, the reason for the problem should be either that you upload an old version of one of the assemblies or that the assembly references in the project point to the 3.0.10 version of Devart.Data.Linq.

1) Check the versions of the assemblies you are uploading to the deployment server. They should be 5.0.349, 3.50.250, 3.0.16 and 3.0.16 for Devart.Data, Devart.Data.SQLite, Devart.Data.Linq and Devart.Data.SQLite.Linq respectively. The assemblies of the proper version should be available in the installation folder (e.g., Program Files\Common Files\Devart\ ).
2) Check the versions the assembly references point to (check the References node of the Solution Explorer tool window). If these are some prior versions, change them to the newer ones or set their 'Specific Version' property to false.
3) Also, you can run a search for the '3.0.10' entry in your solution to check whether the Devart.Data.Linq assembly is referred to somewhere else (for example, if you are using the LinqDataSource component, these may be ASP.NET pages themselves).

Please tell us if this helps.

As for the delay, we have a two business day response policy, though do our best to reply as soon as possible.