5

After installing a Sitecore Update Package via the Update Installation Wizard, there is still a manual step required to active any config files that would be overwritten. Does anyone have a script or other means of activating them all quickly, for cases where you are confident in your config management?

  • Nick, never tried it but we might be able to do something with post deployment step. – ASura Oct 7 '16 at 17:42
5

To do this quickly using PowerShell, without any new tools, see snippet below. It will handle dated packages generated by TDS as well.

# use name of package without .update extension
$packageName = "MyPackage"
get-childitem -recurse -filter "*.config.$($packageName)*" | ? {$_.FullName -notmatch "\\temp\?"} | % { Move-Item $_.FullName $_.FullName.Substring(0, $_.FullName.LastIndexOf(".")) -Force }
4

Have you tried the Sitecore Package Deployer? You basically upload the .update package to a specific folder, it installs it, and then does that whole config activation. I've been using this for my production deploys now for 9 months and it saves so much time and hassle.

  • Jason this would require TDS? – ASura Oct 7 '16 at 17:41
  • 1
    As far as I know it's a free GitHub project that just runs .update packages. The install is a config file and some binaries, from my recollection. I don't believe you need any TDS dlls, but since we use TDS, hard for me to be sure... – Jason St-Cyr Oct 7 '16 at 17:44
  • @JayS You are correct, this module is not dependent on TDS, as update packages are a built-in Sitecore feature. – Dmytro Shevchenko Oct 7 '16 at 20:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.