A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More. 

AI OnAI Off

Deploy CMS 7.1 to production environment

Kristian Ledung
Kristian Ledung
Vote:
 

Hello!

We are about to upgrade from CMS 7 to CMS 7.1. In the installation instructions for CMS 7.1 it says "it is recommended that the update is first done in a test environment, and then deployed to production environment using normal deployment procedures".

I´m comparing our CMS 7 installation with a test installation of CMS 7.1 and the only differences I can see is updated versions of dll:s in the modulesbin folder. Is that the only changes that needs to be deployed for CMS 7.1?

Updated dll:s:

  • EPiServer.CMS.Shell.UI.dll (1.0.431.0 -> 2.1.82.0)
  • EPiServer.Packaging.dll (1.0.1092.0 -> 2.1.90.0)
  • EPiServer.Packaging.UI.dll (1.0.1092.0 -> 2.1.90.0)
  • EPiServer.Shell.UI.dll (1.0.456.0 -> 2.1.90.0)
  • NuGet.Core.dll (2.0.0 ->2.5.0)

New dll:s that only exists in the CMS 7.1 installation:

  • EPiServer.CMS.AddOns.Blocks.dll (1.1.1.0)
  • EPiServer.CMS.Shell.UI.Sources.dll (2.1.82.0)
  • EPiServer.Packaging.Patch1.dll (2.1.90.0)

 

#76041
Oct 16, 2013 9:18
Per Magne Skuseth
Per Magne Skuseth
Vote:
 

The majority of the files are located in the VPP, under "modules" and ""modulesrepository". These will need to get deployed as well. Take a look at this thread:

http://world.episerver.com/Modules/Forum/Pages/Thread.aspx?id=70813

 

edit:incorrect url

#76042
Edited, Oct 16, 2013 9:47
This thread is locked and should be used for reference only. Please use the Episerver CMS 7 and earlier versions forum to open new discussions.
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.