SP2013 vs SP2016 RTM – Diff at assembly level

Here is the latest diff on the SP2016 vs SP2013 code base.  From here you can explore what were some of the more deeper changes in the code.  Biggest changes:

  • All legacy Office Web Apps dlls are now removed
  • Previously I mentioned that silverlight dlls looked to be removed, they are in fact still around
  • Similarly, all the Ceres Search Flow resource dlls are still around
  • Same as last post – All Education dlls are finally removed
  • Still have dependencies on some 3rd party installed dlls:
    • Reporting Services 10.0+
    • Windows Azure Storage
    • Microsoft.Azure.GraphClient.FirstClient – still have no idea where to get this one
    • NewtonSoft.Json 6.0 – used in Search
    • System.Web.Http 5.2.2.0 – used in Search
    • Microsoft.Data (5.3 and 5.6) – seems some dlls have old 5.3 references that have not been updated
  • ChicagoIntegration is gone from RTM – *LOL* [:D]
  • All new Ceres Push API code now exists:
    • Microsoft.Ceres.ContentEngine.ContentPush
    • Microsoft.Ceres.ContentEngine.Operators.ContentPush
    • Microsoft.Ceres.ContentEngine.Processing.ContentPush
    • Microsoft.ContentPushFlow
    • Microsoft.ContentPushHybridFlow
  • New Ceres Flows (for more information on what flows are – see my other post):
    • Microsoft.ContentPushFlow
    • Microsoft.ContentPushHybridFlow
    • Microsoft.ConversationalLatencyFlow
    • Microsoft.CrawlerPropertyReportingSubFlow
    • Microsoft.CrawlerSecurityInsertHybridSubFlow
    • Microsoft.DataLossPreventionSubFlow
    • Microsoft.DeleteTenantFromIndexSystemFlow
    • Microsoft.DocumentPreviewMetadataFeederFlow
    • Microsoft.ExplorerFlow
    • Microsoft.GraphSearchProviderFlow
    • Microsoft.IndexingSubFlow
    • Microsoft.PeopleSuggestionDictionaryDeploymentFlow
      Microsoft.PropertyRetrievalSearchFlow
      Microsoft.QueryCompletionPeopleOutputFlow
      Microsoft.QueryCompletionPersonalizedQueryLogsOutputFlow
      Microsoft.QueryCompletionPreFetchOutputFlow
      Microsoft.QueryCompletionQueryLogsInputFlow
      Microsoft.QueryCompletionQueryLogsOutputFlow
      Microsoft.QuerySuggestionsQueryLogsFlow
      Microsoft.SearchAnalyticsBuzzFeederFlow
      Microsoft.SearchAnalyticsBuzzImportFlow
      Microsoft.SearchAnalyticsBuzzInputFlow
      Microsoft.SearchAnalyticsBuzzOutputFlow
      Microsoft.SearchAnalyticsExternalContentMapFlow
      Microsoft.SearchAnalyticsExternalContentPushFlow
      Microsoft.SearchAnalyticsFollowsImportFlow
      Microsoft.SearchAnalyticsFollowsInputFlow
      Microsoft.SearchAnalyticsGraphIndexFeederFlow
      Microsoft.SearchAnalyticsInFeedInputFlow
      Microsoft.SearchAnalyticsTagsImportFlow
      Microsoft.SearchAnalyticsTagsInputFlow
    • Microsoft.SignalStoreInputFlow
    • Microsoft.UsageAnalyticsImportFlow
  • OfficeGraph API exists:
    • Microsoft.Ceres.External.ContentApi.GraphExtensions
    • Microsoft.Ceres.SearchCore.GraphModel
    • Microsoft.Ceres.SearchCore.GraphQueryModel
    • Microsoft.Ceres.SearchCore.GraphSeedingModel
    • Microsoft.Ceres.SearchCore.GraphServer.Managed
    • Microsoft.Ceres.SearchCore.GraphStatusModel
    • Microsoft.Ceres.SearchCore.Indexes.GraphServerIndex
  • Microsoft.SharePoint.Client.Directory
    • CSOM for the new UserProfile sync stuff
  • Interesting new dll – Microsoft.Office.BigData.DataLoader.*
    • Have no idea what this is, but it looks interesting…
  • New compliance assemblies:
    • Microsoft.Office.CompliancePolicy.Platform

This supplements the following blog posts:

    Enjoy!
    Chris 

    Leave a Reply