Kentico Xperience 13 documentation and ASP.NET Core

Most documentation about running Xperience applications under ASP.NET Core can be found in a dedicated section: Developing Xperience applications using ASP.NET Core. The rest of the documentation still applies, but some code samples and scenarios might need slight modifications for Core projects.

All major differences between the MVC 5 and Core platforms are summarized in Migrating to ASP.NET Core.

×

Export folder structure

Xperience instances organize files used by the administration interface within the CMS folder.

The following list describes the main folders and how they are affected during the import and export process.

ColorMeaning
redSystem folders. Do not make any changes or place your files here unless you want to modify the administration interface.
blueFolders for custom files, part of the export package.
greenFolders for custom files, part of the export package. You may need to create these folders manually.
blackService folders (import files, import/export).
  • Admin 
  • App_Data
    • CMSModules\<module_name> (folders of custom modules)
  • CMSAdminControls
  • CMSEdit
  • CMSFormControls (all form controls selected in the export process are exported with any site)
  • CMSGlobalFiles (exports with any site if the Export global folders option is selected during the export process)
  • CMSImportFiles
  • CMSInstall
  • CMSMasterPages
  • CMSMessages
  • CMSModules
    • <module name> (folders of custom modules)
  • CMSPages
  • CMSResources
  • CMSScripts (CMSScripts\Custom is a folder intended to hold custom JavaScript files for the administration interface, and is part of the export package)
  • CMSSiteUtils
  • CMSVirtualFIles (stores virtual objects when using deployment mode) 
  • CMSWebParts (all web parts selected in the export process are exported with any site; if the web part uses additional files, they must be placed in a folder in format <webpartCodeName>_files; files that are not registered as web parts are not included in the export package)
  • <site code name> (exports with the given site, needs to be created manually or may be created automatically when storing files on the disk; the folder is exported if the Export site folders option is selected during the export process)
    • Files (the default folder for storing files if the system is configured for saving files on the disk)
  • Old_App_Code
    • CMSModules\<module_name> (folders of custom modules)
    • Global (exports with any site, if the Export global folders option is selected during the export process)
    • <site code name> (exports with the given site if the Export site folders option is selected during the export process)
  • Old_App_WebReferences 

Was this page helpful?