Updating nuget packages causes warnings in prepare.bat and build.bat

Updating nuget packages in V3.1 source causes warnings in prepare.bat and build.bat, the warnings shown are:

Build succeeded.

       "C:\Users\Robin\Documents\Visual Studio 2012\Projects\nopCommerce_3.10_S
       ource\build\nop.proj" (default target) (1) ->
       "C:\Users\Robin\Documents\Visual Studio 2012\Projects\nopCommerce_3.10_S
       ource\NopCommerce.sln" (default target) (2) ->
       "C:\Users\Robin\Documents\Visual Studio 2012\Projects\nopCommerce_3.10_S
       ource\Plugins\Nop.Plugin.ExternalAuth.OpenId\Nop.Plugin.ExternalAuth.Ope
       nId.csproj" (default target) (38) ->
       (ResolveAssemblyReferences target) ->
         C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
       (1605,5): warning MSB3247: Found conflicts between different versions of
        the same dependent assembly. [C:\Users\Robin\Documents\Visual Studio 20
       12\Projects\nopCommerce_3.10_Source\Plugins\Nop.Plugin.ExternalAuth.Open
       Id\Nop.Plugin.ExternalAuth.OpenId.csproj]


       "C:\Users\Robin\Documents\Visual Studio 2012\Projects\nopCommerce_3.10_S
       ource\build\nop.proj" (default target) (1) ->
       "C:\Users\Robin\Documents\Visual Studio 2012\Projects\nopCommerce_3.10_S
       ource\NopCommerce.sln" (default target) (2) ->
       "C:\Users\Robin\Documents\Visual Studio 2012\Projects\nopCommerce_3.10_S
       ource\Plugins\Nop.Plugin.ExternalAuth.Facebook\Nop.Plugin.ExternalAuth.F
       acebook.csproj" (default target) (39) ->
         C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
       (1605,5): warning MSB3247: Found conflicts between different versions of
        the same dependent assembly. [C:\Users\Robin\Documents\Visual Studio 20
       12\Projects\nopCommerce_3.10_Source\Plugins\Nop.Plugin.ExternalAuth.Face
       book\Nop.Plugin.ExternalAuth.Facebook.csproj]


       "C:\Users\Robin\Documents\Visual Studio 2012\Projects\nopCommerce_3.10_S
       ource\build\nop.proj" (default target) (1) ->
       "C:\Users\Robin\Documents\Visual Studio 2012\Projects\nopCommerce_3.10_S
       ource\NopCommerce.sln" (default target) (2) ->
       "C:\Users\Robin\Documents\Visual Studio 2012\Projects\nopCommerce_3.10_S
       ource\Tests\Nop.Web.MVC.Tests\Nop.Web.MVC.Tests.csproj" (default target)
        (15) ->
         C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
       (1605,5): warning MSB3247: Found conflicts between different versions of
        the same dependent assembly. [C:\Users\Robin\Documents\Visual Studio 20
       12\Projects\nopCommerce_3.10_Source\Tests\Nop.Web.MVC.Tests\Nop.Web.MVC.
       Tests.csproj]

    3 Warning(s)

I guess it is either the Microsoft.Bcl.Build or Microsoft.Net.Http as these are the only packages updated in Nop.Plugin.ExternalAuth.Facebook.


Question 1> will this cause any adverse effect if I deploy the project?
Question 2> was it a good idea to update the packages in the first place?
Question 3> does anyone know of how to fix the warnings?

Version 3.1 deploy warnings.

I am also getting the same 3 warnings. At first it was only 1 microsoft.bcl.build warning. After correctly referencing and updating the package there are now the three warnings you posted. I have no answers to your questions as I have the same questions.

Andrei? Any answers? This is something that should be addressed.

I managed to fix this by editing each of the csproj files and removing the references so they look like that of the original file.

This removed the warnings in the bat files and still kept the compiler working without warnings as well

networkfusion,

could you be a little more specific?

"I managed to fix this by editing each of the csproj files and removing the references so they look like that of the original file."

OK. All problems solved.

In debug mode this warning is always present but it can be ignored.

"All projects referencing Nop.Web.csproj must install nuget package Microsoft.Bcl.Build. Nop.Web.MVC.Tests"

Nop.Web.MVC.Tests is not deployed so the warning is moot.

Running deploy.bat in debug mode produces recaptcha errors so it is not deployed.

Running deploy.bat in release mode produces no warnings, no errors and s successful build.