top of page

SharePoint 2016 App Store Deploy Button

  • Writer: Jeremiah
    Jeremiah
  • Sep 14, 2018
  • 1 min read

In the initial deployment of our development region we had a successful and functioning SharePoint App store. We decide to deploy September 2017 CU to this region so that our developers could take advantage of Feature Pack 2. Just like everything else it should be straight forward and then there is the but. We are not talking smoked pigs butt here, this is the Microsoft but nothing is normal and easy.


This should be easy but...

With SharePoint 2016 Microsoft decided to split the patches out into two separate files. One for language dependent files and one for language independent files. This is to make the patching process faster, well we thought we are not using any other languages in our farm we will just install the independent files and save some time.

This was great everything worked until we decided to deploy a new app to the app store. The Deploy button wouldn't work and it wasn't named deploy anymore it was named "$Resources,Client_Component_Deploy_Ribbon_Button".

Many emails went between us and Microsoft before we decided to apply the Language dependent patch for September. Once this was applied the Deploy button was back to what it should be.


Lesson we learned breaking the patches out wasn't meant to save time in the entire patching process just in the downloading of the files.


Happy SharePointing!!!!

Comments


Join our mailing list

  • Black Facebook Icon
  • Black Twitter Icon
  • Black Pinterest Icon
  • Black Flickr Icon
  • Black Instagram Icon

© 2023 by The Mountain Man. Proudly created with Wix.com

bottom of page