Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Conflicts between different versions of the same assembl
Message
From
14/09/2010 11:18:16
 
 
To
14/09/2010 09:48:55
Timothy Bryan
Sharpline Consultants
Conroe, Texas, United States
General information
Forum:
ASP.NET
Category:
The Mere Mortals .NET Framework
Miscellaneous
Thread ID:
01480863
Message ID:
01481124
Views:
17
>>>>>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.

Frank Cazabon
Samaan Systems Ltd.
www.samaansystems.com
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform