Invalid assembly versions with 2014.R1

0 votes
asked Mar 4, 2014 by SeToY (520 points)
edited Nov 25, 2014

Hello,

I'm getting the following build warning after upgrading. This might be due to the different version numbers in the Ftp and SecureMail libraries.

29>------ Build started: Project: Company.Product.Sub, Configuration: Debug Any CPU ------
27>  No way to resolve conflict between "Rebex.Networking, Version=3.0.5171.0, Culture=neutral, PublicKeyToken=1c4638788972655d" and "Rebex.Networking, Version=3.0.5085.0, Culture=neutral, PublicKeyToken=1c4638788972655d". Choosing "Rebex.Networking, Version=3.0.5171.0, Culture=neutral, PublicKeyToken=1c4638788972655d" arbitrarily.
27>  No way to resolve conflict between "Rebex.Common, Version=2.0.5171.0, Culture=neutral, PublicKeyToken=1c4638788972655d" and "Rebex.Common, Version=2.0.5085.0, Culture=neutral, PublicKeyToken=1c4638788972655d". Choosing "Rebex.Common, Version=2.0.5171.0, Culture=neutral, PublicKeyToken=1c4638788972655d" arbitrarily.
27>  Consider app.config remapping of assembly "Rebex.Networking, Culture=neutral, PublicKeyToken=1c4638788972655d" from Version "3.0.5085.0" [] to Version "3.0.5171.0" [D:\Private\Source\Product\Main\Frameworks\Company.Project\bin\Debug\Rebex.Networking.dll] to solve conflict and get rid of warning.
27>  Consider app.config remapping of assembly "Rebex.Common, Culture=neutral, PublicKeyToken=1c4638788972655d" from Version "2.0.5085.0" [] to Version "2.0.5171.0" [D:\Private\Source\Product\Main\Frameworks\Company.Project\bin\Debug\Rebex.Common.dll] to solve conflict and get rid of warning.
27>C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(1635,5): warning MSB3276: Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190.
27>  Company.Product.Tools.ConfigurationManager -> D:\Private\Source\Product\Main\Tools\Company.Product.Tools.ConfigurationManager\bin\Debug\ConfigurationManager.exe
29>  No way to resolve conflict between "Rebex.Common, Version=2.0.5171.0, Culture=neutral, PublicKeyToken=1c4638788972655d" and "Rebex.Common, Version=2.0.5085.0, Culture=neutral, PublicKeyToken=1c4638788972655d". Choosing "Rebex.Common, Version=2.0.5171.0, Culture=neutral, PublicKeyToken=1c4638788972655d" arbitrarily.
29>  Consider app.config remapping of assembly "Rebex.Common, Culture=neutral, PublicKeyToken=1c4638788972655d" from Version "2.0.5085.0" [] to Version "2.0.5171.0" [D:\Private\Source\Product\Main\packages\Rebex.2014.R1\lib\net40\Rebex.Common.dll] to solve conflict and get rid of warning.
29>  Consider app.config remapping of assembly "Rebex.Networking, Culture=neutral, PublicKeyToken=1c4638788972655d" from Version "3.0.5085.0" [] to Version "3.0.5171.0" [D:\Private\Source\Product\Main\packages\Rebex.2014.R1\lib\net40\Rebex.Networking.dll] to solve conflict and get rid of warning.
Applies to: Rebex Secure Mail

1 Answer

0 votes
answered Mar 4, 2014 by Tomas Knopp (58,890 points)
edited Mar 4, 2014

Hello,

with more than one Rebex component in a project, you have to use the same version of the assemblies. So if one of your support contract is expired (I was unable to check your support contracts, as your email address cannot be found in our system), a renewal might be needed here in order to get the latest version of assemblies for both components.

You might also check the checklist for upgrading to newer version of Rebex assemblies.

commented Mar 4, 2014 by SeToY (520 points)
edited Mar 4, 2014

Oh, I see. Rebex File Transfer Pack for .NET has not yet been released in version 2014R1, am I right? Since I'm using Rebex Secure Mail for .NET and Rebex File Transfer Pack for .NET simultaneously.

commented Mar 4, 2014 by Tomas Knopp (58,890 points)
edited Mar 4, 2014

No, we have released all Rebex components in 2014R1 version. This is a standard practice.

So are you using latest 2014R1 version of both Rebex File Transfer Pack for .NET and Rebex Secure Mail for .NET? If yes, please follow these instructions to make sure the references are all right:

Steps to replace old version with newer version:

  1. Remove the references to the old version dlls from your project.
  2. Replace old version dlls with the new version dlls.
  3. Add references to the new dll files to your project.
  4. Recompile your project.
...