BorlandTalk.com

Jeff · Guest

I have an ASP.NET app that was developed with Delphi 2005 SP 1. It runs
fine on my development machine, but when I deploy it to the server I get
the following error, when trying to run it: I have checked the
assemblies and they are all in version. I copied the
Borland.Data.Provider.dll to the bin folder and made sure CopyLocal was
checked before compiling the app. What else do I need to check?

TIA

The located assembly's manifest definition with name
'Borland.Data.Provider' does not match the assembly reference.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.

Exception Details: System.IO.FileLoadException: The located assembly's
manifest definition with name 'Borland.Data.Provider' does not match the
assembly reference.

Source Error:

An unhandled exception was generated during the execution of the current
web request. Information regarding the origin and location of the
exception can be identified using the exception stack trace below.

Assembly Load Trace: The following information can be helpful to
determine why the assembly 'Borland.Data.Provider' could not be loaded.

=== Pre-bind state information ===
LOG: DisplayName = Borland.Data.Provider, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=91d62ebb5b0d1b1b
(Fully-specified)
LOG: Appbase = file:///E:/CFACEC
LOG: Initial PrivatePath = bin
Calling assembly : CEC, Version=2.0.1822.28298, Culture=neutral,
PublicKeyToken=null.
===

LOG: Publisher policy file is not found.
LOG: No redirect found in host configuration file
(C:WINNTMicrosoft.NETFrameworkv1.1.4322aspnet.config).
LOG: Using machine configuration file from
C:WINNTMicrosoft.NETFrameworkv1.1.4322configmachine.config.
LOG: Post-policy reference: Borland.Data.Provider, Version=2.0.0.0,
Culture=neutral, PublicKeyToken=91d62ebb5b0d1b1b
LOG: Attempting download of new URL
file:///C:/WINNT/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
Files/cfacec/c705b00e/71fd9125/Borland.Data.Provider.DLL.
LOG: Attempting download of new URL
file:///C:/WINNT/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET
Files/cfacec/c705b00e/71fd9125/Borland.Data.Provider/Borland.Data.Provider.DLL.
LOG: Attempting download of new URL
file:///E:/CFACEC/bin/Borland.Data.Provider.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Minor Version

Stack Trace:

[FileLoadException: The located assembly's manifest definition with name
'Borland.Data.Provider' does not match the assembly reference.]
login.TLogin.InitializeComponent() +0
login.TLogin.OnInit(EventArgs e)
System.Web.UI.Control.InitRecursive(Control namingContainer) +240
System.Web.UI.Page.ProcessRequestMain() +197

--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:1.1.4322.2032;
ASP.NET Version:1.1.4322.2032

Frede · Guest

I have the EXACT same problem. Works fine on development machine but not
when deployed. I have posted this on QualityCentral (# 10252). i wish
someone from Borland could comment on this asap.

This is the post:
Delphi 2005 with Update 1. ASP.NET project using Borland BDP

The project is running fine on the development machine but when deployed to
another server the following error is displayed
"The located assembly's manifest definition with name
'Borland.Data.Provider' does not match the assembly reference."

Loading the projects dll in Lutz Reflector show the following information
under references/Borland.Data.Provider
// Assembly Reference Borland.Data.Provider
Version: 2.0.0.0
Name: Borland.Data.Provider, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=91d62ebb5b0d1b1b

Although in D2005 under references the version of the
Borland.Data.Provider.dll is 2.1.0.0 not 2.0.0.0

I have checked the project file and it is correct (references the
borland.data.provider.dll in bds3.0 which is version 2.1.0.0
The gac contain versions 1.5.1.0 and 2.1.0.0 of the dll, no sign of any
2.0.0.0 version
I have tried copy local on and off with complete rebuild but does not make
any difference.

If i open "c:program
filesborlandbds3.0libBorland.Data.Provider.dcpil" with notepad I see
that is referencing 2.0.0.0 and not 2.1.0.0

Maybe this is the problem.

On Mon, 27 Dec 2004 15:52:33 -0600, Jeff wrote:

Frede · Guest

A colleague of mine found a solution to the problem:

Add the following Assembly rebind to your web.config.

<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Borland.Data.Provider"
publicKeyToken="91d62ebb5b0d1b1b" culture="neutral" />
<bindingRedirect oldVersion="2.0.0.0" newVersion="2.1.0.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="Borland.Data.Common"
publicKeyToken="91d62ebb5b0d1b1b" culture="neutral" />
<bindingRedirect oldVersion="2.0.0.0" newVersion="2.1.0.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>

It tells your app to use version 2.1.0.0 instead of 2.0.0.0 (which is what
is causing the problem). If you only add it for Data.Provider you'll get
the same problem with Data.Common so you need to add that as well

On Tue, 11 Jan 2005 11:50:48 +0100, Frede wrote: