>>>>>>Hi,
>>>>>>
>>>>>>I've been experimenting with Web, WPF and Winforms User Interfaces for a project. Now that I've added the Winforms project to my solution (which has a WPF and a Web UI project as well) I get this warning:
>>>>>>
>>>>>>Found conflicts between different versions of the same dependent assembly.
>>>>>>
>>>>>>How do I work out which ones are conflicting?
>>>>>>
>>>>>>Maybe this is also related to why my error messages show that I am using .NET 2.0 in the Web project, when I have the projects set to use .NET 3.5?
>>>>>
>>>>>No ideas from anyone? :(
>>>>
>>>>I have run into this before. It can be a couple different things and usually takes looking for the extra assembly or reference. Make sure you don't have any extra assemblies laying around in your bin folder. Also the web.config file may have a old reference in there.
>>>>Tim
>>>
>>>
>>>How do I know what an "extra assembly" is? Could the old reference be in the app.config as well?
>>
>>Yes,
>>And if you look in the bin folder where your application is stored you would see the *.dll files in there. If there is an older mm dll file in there, just delete it out.
>>Tim
>
>I don't see anything that looks strange.
>
>1. What do you mean by an "extra assembly"?
>
>2. What do you mean by an "older mm dll"? Older than what?

Frank,

You are looking for something like one line referencing mm .net 2.0 and another referencing mm .net 3.5 in any of the config files. Also, in your solution, you want to make sure that you don't have a reference to OakLeaf.MM2008.Interfaces and another to OakLeaf.MM2006.Interfaces or something like that. You can only have one mm .net version referenced in your solution.
It just takes slogging through all the different places those references can be. Good luck.