This is a ASP.NET MVC web application with the Kentico EMS Page builder functionality turned on. This repository is used as a source for a nuget package that eriches the component project with an MVC app environment for component development.
This repo is still in development. It is about to be released after the Kentico 12 Service pack is released.
-
Download Kentico installation exe file
-
Install Kentico using the command line.
-
Use provided Kentico installation profile template and define
TargetFolderattribute of thIIStag (:warning: Do not use the same location as the one you have you exe file located)- This will install Kentico Administration interface without any site
- If you wish to adjust the connection to the different database server, adjust the
SQLtag in the configuration - If you wish to add your license to the instance, adjust the
Licensestag in the configuration XML
.\Kentico_12_0_trial.exe KenticoInstallationProfile.xmlIf you get an error about already installed program files run command for uninstalling the current program files and then run the previous command again
.\Kentico_12_0_trial.exe /u
-
-
Apply the latest hotfix (or at least 12.0.29) (Service Pack)
-
Download this repository and extract it under the target folder (
TargetFolder) that was defined in previous stepThe content should looks like this
. ├── CMS ├── WebApp.sln ├── Lib ├── DevelopmentSite ├── DevelopmentSite.sln ├── GlobalAssemblyInfo.cs ├── README.md └── ... -
Run the administration instance (already registered in IIS with
_Adminsuffix) and import the site export package according to the (documentation)- This package contains
- Site (With
Presentation URL) - Page type (configured for page builder - url pattern
/and use tab checkbox) - Page by this page type
- Automatic web farms
- Site (With
- This package contains
-
Adjust connection strings + hash string salt from /CMS/web.config to [/DevelopmentSite/ConnectionStrings.config] and [/DevelopmentSite/Appsettings.config]
-
Register
Development applicationin IIS/IIS Express- use
<TargetFolder>/DevelopmentSiteas aPhysical path - you could use the same Application pool as is set f administration application
- use
-
Adjust presentation URL in the administration instance according to the registration from the previous step
-
Build
DevelopmentSitein Visual Studio