Are We moving from dll hell to Nuget Package Hell ?

%3CLINGO-SUB%20id%3D%22lingo-sub-52487%22%20slang%3D%22en-US%22%3EAre%20We%20moving%20from%20dll%20hell%20to%20Nuget%20Package%20Hell%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52487%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20trying%20to%20compile%20SharePointPnP.Powershell%20and%20I%20am%20getting%20this%20message%20%3A-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EError%26nbsp%3BCS1705%26nbsp%3BAssembly%20'Microsoft.SharePoint.Client'%20with%20identity%20'Microsoft.SharePoint.Client%2C%20Version%3D16.1.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3D71e9bce111e9429c'%20uses%20'Microsoft.SharePoint.Client.Runtime%2C%20Version%3D16.1.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3D71e9bce111e9429c'%20which%20has%20a%20higher%20version%20than%20referenced%20assembly%20'Microsoft.SharePoint.Client.Runtime'%20with%20identity%20'Microsoft.SharePoint.Client.Runtime%2C%20Version%3D16.0.0.0%2C%20Culture%3Dneutral%2C%20PublicKeyToken%3D71e9bce111e9429c'%26nbsp%3BSharePointPnP.PowerShell.Tests%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20it%20would%20appear%20that%20the%20Nuget%20Packages%20have%20gotten%20themselves%20out%20of%20sync.%26nbsp%3B%20I%20have%20about%2043%20errors%20like%20this%20one.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20have%20thought%20by%20now%20we%20would%20not%20get%20this%20sort%20of%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20I%20was%20wrong%20!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-52487%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPnP%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52652%22%20slang%3D%22en-US%22%3ERe%3A%20Are%20We%20moving%20from%20dll%20hell%20to%20Nuget%20Package%20Hell%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52652%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20turns%20out%20all%20of%20the%20problems%20were%20in%20SharePointPnP.PowerShell.Tests.%3C%2FP%3E%3CP%3EI%20went%20through%20all%20of%20the%20references%20and%20change%20the%2016.0.0.0%20-%26gt%3B%2016.1.0.0%3C%2FP%3E%3CP%3EThen%20worked%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESharePointPnP.PowerShell.ModuleFilesGenerator%20and%20SharePointPnP.PowerShell.Commands%20were%20at%2016.1.0.0%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F122%22%20target%3D%22_blank%22%3E%40Erwin%20van%20Hunen%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52539%22%20slang%3D%22en-US%22%3ERe%3A%20Are%20We%20moving%20from%20dll%20hell%20to%20Nuget%20Package%20Hell%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52539%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Erwin%3C%2FP%3E%3CP%3EYes%2C%20I%20have%20a%20clone%20of%20the%20PnP%20Site%20Core%20Repository.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%2C%20I%20did%20update%20that%20repo%20before%20trying%20to%20compile%20the%20PowerShell%20project.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20PnP%20Site%20Core%20Repository%20compiled%20successfully.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20was%20the%20PnP%20Powershell%20repo%20which%20failed.%26nbsp%3B%20I%20updated%20the%20references%20and%20it%20all%20compiled.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20I%20should%20not%20need%20to%20do%20that%20should%20I%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENigel%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-52533%22%20slang%3D%22en-US%22%3ERe%3A%20Are%20We%20moving%20from%20dll%20hell%20to%20Nuget%20Package%20Hell%20%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-52533%22%20slang%3D%22en-US%22%3EIn%20this%20case%20we%20don't%20use%20nuget%20packages%20for%20the%20CSOM%20sdk.%20We%20refer%20to%20them%20from%20the%20PnP%20Sites%20Core%20repository%2C%20which%20is%20the%20reason%20we%20require%20a%20clone%20of%20that%20repository%20too%20on%20your%20machine.%20Did%20you%20update%20that%20repo%20too%20before%20you%20tried%20to%20compile%20the%20PowerShell%20project%3F%3C%2FLINGO-BODY%3E
Contributor

I am trying to compile SharePointPnP.Powershell and I am getting this message :-

 


Error CS1705 Assembly 'Microsoft.SharePoint.Client' with identity 'Microsoft.SharePoint.Client, Version=16.1.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' uses 'Microsoft.SharePoint.Client.Runtime, Version=16.1.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' which has a higher version than referenced assembly 'Microsoft.SharePoint.Client.Runtime' with identity 'Microsoft.SharePoint.Client.Runtime, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' SharePointPnP.PowerShell.Tests 

 

So it would appear that the Nuget Packages have gotten themselves out of sync.  I have about 43 errors like this one.

 

I would have thought by now we would not get this sort of problem.

 

But I was wrong !

3 Replies
In this case we don't use nuget packages for the CSOM sdk. We refer to them from the PnP Sites Core repository, which is the reason we require a clone of that repository too on your machine. Did you update that repo too before you tried to compile the PowerShell project?

Hi Erwin

Yes, I have a clone of the PnP Site Core Repository.

 

Yes, I did update that repo before trying to compile the PowerShell project.

 

The PnP Site Core Repository compiled successfully.  

 

It was the PnP Powershell repo which failed.  I updated the references and it all compiled.

 

But I should not need to do that should I ?

 

Nigel

 

It turns out all of the problems were in SharePointPnP.PowerShell.Tests.

I went through all of the references and change the 16.0.0.0 -> 16.1.0.0

Then worked fine.

 

SharePointPnP.PowerShell.ModuleFilesGenerator and SharePointPnP.PowerShell.Commands were at 16.1.0.0

 

@Erwin van Hunen