SharePoint Development Owner todayJuly 22, 2019 16 1
This is more a short, off the cuff tip than an expansive post about satellite get’s with TFS. When developing local SharePoint projects, it is significant to remember when leaning on the automated package features in VS.NET that satellite assemblies may not be natively bundled into a solution by merely ensuring that the satellite reference is tagged has the Copy Local property set to true. Even if you ensure that the manifest for the solution has the suitable Assemblies element reference:
this will still not pickup the orphaned assembly. To get around this, use the Package Designer under the Advanced tab. In this dialog, there is a particular section for adding additional assemblies to the project package. Add the assemblies in question to this section, and you should be good to go!
Written by: Owner
Tagged as: SharePoint, net, projects, Microsoft, Optimize SharePoint, Deployment, XML, VS.NET, design, TFS, satellite assembly, property, assembly, project, reference, feature, features, additional, solution, quest, question, addition, designer, location, package, sec, section, SharePoint Projects.