Databases
StackOverflow2013
Postsdbo
POIssue with debugging app using MQ-Websphere : amqmdnet.dll due to Version conflict
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIssue with debugging app using MQ-Websphere : amqmdnet.dll due to Version conflict
    primarykey
    data
    text
    <p>I have an App that references the IBM-WebSphereMQ dll "amqmdnet.dll". I'm trying to debug this Console Application locally, for which I got the 64 bit dll from our OP's team.The server that the service is running on is 32 bit. When trying to debug through, I get the following error.</p> <blockquote> <p>Could not load file or assembly 'amqmdnet, Version=1.0.0.3, Culture=neutral, PublicKeyToken=dd3cb1c9aae9ec97' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)</p> </blockquote> <p>The version of the dll givem to me was 7.1.0.0. I have added references in the solution to the version 7.1.0.0 I'm not sure where it is expecting the 1.0.0.3 version from? I tried adding the following to my App.Config:</p> <pre><code>&lt;runtime&gt; &lt;assemblyBinding&gt; &lt;dependentAssembly&gt; &lt;assemblyIdentity name="amqmdnet" publicKeyToken="dd3cb1c9aae9ec97"/&gt; &lt;bindingRedirect oldVersion="1.0.0.3" newVersion="7.1.0.0"/&gt; &lt;/dependentAssembly&gt; &lt;/assemblyBinding&gt; &lt;/runtime&gt; </code></pre> <p>but, to no effect. It still gives me the same exception. Here is the "Fusionlog" generated during the 'probing' time:</p> <blockquote> <pre><code>=== Pre-bind state information === LOG: User = xxxx\ccc LOG: DisplayName = amqmdnet, Version=1.0.0.3, Culture=neutral, PublicKeyToken=dd3cb1c9aae9ec97 (Fully-specified) LOG: Appbase = file:///C:/xxx/vvv/MouserMQ/services/MMQMonitor/dev/Kk/MMQconfigChange/MMQWatchDogConsole/bin/Debug/ LOG: Initial PrivatePath = NULL Calling assembly : MMQTools, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null. === LOG: This bind starts in default load context. LOG: Using application configuration file: C:\NewCodeBase\mm\MouserMQ\services\MMQMonitor\dev\kk\MMQconfigChange\MMQWatchDogConsole\bin\Debug\MMQWatchDogConsole.vshost.exe.Config LOG: Using host configuration file: LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config. LOG: Post-policy reference: amqmdnet, Version=1.0.0.3, Culture=neutral, PublicKeyToken=dd3cb1c9aae9ec97 LOG: Attempting download of new URL file:///C:/nb/Mouser/MouserMQ/services/MMQMonitor/dev/kk/MMQconfigChange/MMQWatchDogConsole/bin/Debug/amqmdnet.DLL. WRN: Comparing the assembly name resulted in the mismatch: Major Version ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated. </code></pre> </blockquote> <p>Is there something else I'm missing? I deleted and re-added the references to the dll wherever it appears in my solution.</p> <p>Can someone help me with this? I'd really appreciate any help :)</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USkarry
    1. USkarry
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload