Found conflicts between different versions of the same dependent assembly

-

I am currently developing a .NET 2.0 application, which consists of 10+ projects.

The problem is that, if I include an external component always get the following warning while building: Can see only one line message in errors window like below,

"Found conflicts between different versions of the same dependent assembly".

What exactly does this warning mean and is there a possibility to exclude this warning? OR
How to find which assembly actually this warning referring to?

Resolution:

=>> How to find the exact details of dependent assembly the warning is referring,
Change the "MSBuild project build output verbosity" to "Detailed" or above. To do this, follow these steps:
  1. Bring up the Tools/Options dialog (Tools->Options...).
  2. In the left-hand tree, select the Projects/Solutions node, and then select Build and Run.
    • Note: if this node doesn't show up, make sure that the checkbox at the bottom of the dialog ("Show all settings") is checked.
  3. In the tools/options page that appears, set the MSBuild project build output verbosity level to "Detailed" (assuming you're on VS2010; "Normal" will suffice in VS2008 or older).
  4. Build the project and look in the output window.
Now you can find as trace like the following,
Target ResolveAssemblyReferences:
    Consider app.config remapping of assembly "NUnit.Framework.dll, ..." 
        from Version "2.4.8.0" to "NUnit.Framework.dll Version "2.5.0.0" ......
        to solve conflict and get rid of warning.
    C:\WINDOWS\Microsoft.NET\Framework\v2.0\Microsoft.Common.targets : 
        warning MSB3247: Found conflicts between different versions of the same dependent assembly.


My specific case was an incorrect reference to NUnit.Framework. See above, I had two projects referencing two different versions of NUnig. I went to the project with the older version, removed the reference, then added the correct reference. Now it is working fine without this warning..

Comments

Post a Comment

Popular posts from this blog

Auto Scroll in Common Controls

-
This example shows, how to programatically autoscroll WinForm controls TextBox, ListBox, ListView, TreeView and DataGridView. Autoscroll to the end of box or view is useful. For example, in situations when you use one of these components as the output log window. Usually you add the items to the box or view and you want to be sure that the recently added item is visible without the necessary to do it manually. Though it is not difficult to solve this problem, .NET doesn't provide any unified way how to do it. TextBox autoscroll Code: textBox1.SelectionStart = textBox1.Text.Length; textBox1.ScrollToCaret(); ListBox autoscroll Code: listBox1.SelectedIndex = listBox1.Items.Count - 1; listBox1.SelectedIndex = -1; ListView autoscroll Code: listView1.EnsureVisible(listView1.Items.Count - 1); TreeView autoscroll Code: treeView1.Nodes[treeView1.Nodes.Count - 1].EnsureVisible(); DataGridView autoscroll Code: dataGridView1.FirstDisplayedCell = ...
Read more

Convert typed library (.tlb) to .net assembly?

-
Sometimes we have to use the legacy code(C, C++) in .Net projects which is provided by third party vendors. Most of the times these guys will provide, equivalent .net framework typed library (.tlb) of that legacy code. Then, how to refer those in our .net projects and make use of functionality provided by it?   Follow the below steps, Keep ".tlb" file which is nothing but legacy typed library Open windows command prompt Go to directory, " C:\Program Files (x86)\Microsoft Visual Studio 8\SDK\v2.0\Bin " or     "C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin". It depends on which version of visual studio you had. Enter the following and execute, TlbImp.exe "E\MyLibrary.tlb" . Here, replace "E:\MyLibrary.tlb" with path to your tlb file. It will import the .net framework type library to assembly.i.e, .dll and it can be found at path "C:\Program Files (x86)\Microsoft Visual Studio 8\SDK\v2.0\Bin" with name ...
Read more

Disable close button on form - C#

-
In one of my projects, I had to implement a form with Close[X] button Hide, so that the user cannot leave the form until it finishes the data processing. From the form designer window in VS.Net 2005, it is possible to hide the Minimize box and Maximize box. But there is no property called Close or CloseBox. Then I had tried with by setting form property ControlBox = false . With this i am able to achieve hiding the Close/Minimize/Maximize buttons. But at the same time there is a side effect.i.e., Form icon(which is generally displayed on form title bar)  also hidden.  So after little bit investigation came up with the following hack to get,  i)  disable the close button  ii) displaying the form icon To achieve this, we have to override CreateParams property of Form base class as follows, Code: private const int CP_DISABLE_CLOSE_BUTTON = 0x200; protected override CreateParams CreateParams { get ...
Read more