Dependent assemblies have version conflicts

[Eric]

After attempting to build a solution, I receive the error message; "One or
more dependent assemblies have version conflicts" "Do you want to fix these
conflicts by adding binding redirect records in the app.config file?"

I received this after changing the assembly version in two of the solution's
projects to [assembly: AssemblyVersion("1.0.0.0")]

What does this error mean?

 

[Bruce Wood]

Is this in VS2005, or VS2003?

 

[Gary Chang[MSFT]]

Hi Eric,

What does this error mean?

Version conflicts could be caused by when an assembly is shared by two or
more applications. For example, Application A and Application B may both
use the Widget1 component. If a new version of Application A has been
released that uses a later version of the Widget1 component.Application B
might fail when the new version of the Widge1t component is not 100%
compatible with Application B. This situation is previously referred to as
"DLL hell."

After attempting to build a solution, I receive the error
message; "One or more dependent assemblies have
version conflicts" "Do you want to fix these conflicts by
adding binding redirect records in the app.config file?"

Would you please provide more a detailed description about this problem?

For which projects did you change the version numbers, what numbers were
their previous version's, how do you reference these 2 projects in your
solutions?

By the way, do you use the VS2005 in this case?


Best regards,

Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng2006 when prompted. Once you have entered the
secure code mmpng2006, you will be able to update your profile and access
the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================

 

[Eric]

Sorry about that, I should have mentioned that this is VS2005.

I have two projects that are collections of Composite Controls. One of the
projects is specific to the current solution I'm working on, the other is
re-used in multiple solutions.

Previously the values in the two projects were set to the defaults
[assembly: AssemblyVersion("1.0.*")]

I changed this to [assembly: AssemblyVersion("1.0.0.0")] based on a response
to another problem I was receiving. Please see thread "Designer
LoaderExecptions"
microsoft.public.dotnet.framework.windowsforms.controls .

Setting explicit values for the assembly versions was the solution to the
above problem but has now caused the error I've reported here.


Hope this helps clear things up.

Hi Eric,

What does this error mean?

Version conflicts could be caused by when an assembly is shared by two or
more applications. For example, Application A and Application B may both
use the Widget1 component. If a new version of Application A has been
released that uses a later version of the Widget1 component.Application B
might fail when the new version of the Widge1t component is not 100%
compatible with Application B. This situation is previously referred to as
"DLL hell."

After attempting to build a solution, I receive the error
message; "One or more dependent assemblies have
version conflicts" "Do you want to fix these conflicts by
adding binding redirect records in the app.config file?"

Would you please provide more a detailed description about this problem?

For which projects did you change the version numbers, what numbers were
their previous version's, how do you reference these 2 projects in your
solutions?

By the way, do you use the VS2005 in this case?


Best regards,

Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng2006 when prompted. Once you have entered
the
secure code mmpng2006, you will be able to update your profile and access
the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
======================================================

 

[Eric]

VS2005

 

[Gary Chang[MSFT]]

Hi Eric,

I have two projects that are collections of Composite Controls.
One of the projects is specific to the current solution I'm working
on, the other is re-used in multiple solutions.

I got it. That means after you specified one Winform usercontrol assembly's
version to 1.0.0.0, you got the "version conflicts" error when building its
solution.

According to the error "version conflicts", it appears some of that
solution's projects require a different version of the target assembly. In
this scenario, I think you need to find out which projects in that solution
cause the problem. You can build that solution's project one by one to
locate them.

By the way, have you tried any higher version to your assembly, such as
"2.0.0"?


Thanks!

Best regards,

Gary Chang
Microsoft Community Support
======================================================
PLEASE NOTE the newsgroup SECURE CODE and PASSWORD will be updated at 9:00
AM PST, February 14, 2006. Please complete a re-registration process by
entering the secure code mmpng2006 when prompted. Once you have entered the
secure code mmpng2006, you will be able to update your profile and access
the partner newsgroups.
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================