glapointe
commented
9 years ago I definitely think this approach would be much better. I didn't actually intend for the assemblies to get added to the repo - I just forgot to add an ignore for them (everything but the MAML assembly at least which I need to include with the project). I'll look into changing it to match this pattern. Thanks!
The post build script
GenerateHelp.ps1(when it calls the classLapointe.PowerShell.MamlGenerator.CmdletHelpGenerator) requires the presence of two assemblies specific to the SharePoint version for each project:Microsoft.SharePoint.Client.ServerRuntime.dllMicrosoft.SharePoint.Library.dllThe assemblies in the ReferenceAssemblies folder allow building (and packaging) the cmdlet projects on a dev or build machine without having either version of SharePoint installed. However, these two assemblies are missing from both projects' ReferenceAssemblies folder.
As a result, the Build-WSPs.ps1 script reports one of two errors on a dev or build machine that does not have the corresponding version of SharePoint installed, depending on which of these two assemblies is missing.
For example, for the Lapointe.SharePoint2010.PowerShell project:
or
The solution is simple: ensure that these two assemblies can be found by the build engine. In keeping with the approach in this repo, add the two SharePoint version specific assemblies to each projects' ReferenceAssemblies folder.
Note, I'm fairly sure it is not permitted to redistribute Microsoft's SharePoint assemblies in this way. It would be more appropriate to provide a list of the required assemblies for the build and instructions on where to store them. On the other hand, there is definite value in having everything in place in the repo so it builds right away without any additional configuration.
For example, How to Build Office Developer Tools Projects with TFS Team Build 2012 explains how to set up a one-time global folder eg
C:\Program Files\Reference Assemblies\Microsoft\SharePoint 2013\and register this using a new registry keySharePoint 2013under the branchHKEY_LOCAL_SYSTEM\SOFTWARE\Microsoft\.NETFramework\ v4.0.30319\AssemblyFoldersEx\. The equivalent for SharePoint 2010 is the registry branchHKEY_LOCAL_SYSTEM\SOFTWARE\Microsoft\.NETFramework\v2.0.50727\AssemblyFoldersEx.According to How to: Add or Remove References By Using the Add Reference Dialog Box, the .NET framework version number in the registry branch is VersionMinimum, a lower bound value:
So it might be more appropriate to use v3.5 and v4.5 for SharePoint 2010 and SharePoint 2013, respectively. I only tested it using the 4-part version number.