Page Comparison

...

Select ASP.Net Web Application as the project type

Choose the MVC template

Install Lynicon

To install Lynicon as find it is not currently in the NuGet library, you will need to set up a local Nuget feed which is described here.

Image Removed

Open the NuGet Package Manager and select the Local package source, choose Nuget Gallery on nuget.org

Image Added

Choose Lynicon.Identity package.  This automatically performs all the steps in Manual Installation and Generic ASP.Net Identity.

...

Set the Connection String to the Database

Determine a SQL database locally or remote which will host the content and user data.  In web.config, set the value for the connection string element which has been created by the installation, and also the DefaultConnection connection string which already existed (ensuring user tables are created in the same database as content tables):

  <connectionStrings>
    <add name="DefaultConnection" connectionString="..."  providerName="System.Data.SqlClient" />
    <!-- Add lynicon database connection string here, or delete if no database being used -->
    <add name="LyniconContent" connectionString="..." />
  </connectionStrings>

Run the SQL script at /Areas/Lynicon/Admin/SQL/LyniconCoreInit.sql against the database to create the initial tables for Lynicon.

Set up an Admin User

Run the site locally. On the home page the template has created, select Register in the top black bar at the right to create a user account which will be the initial admin user.  Fill in the form this takes you to:

Image Removed

This will create a user record, but in order to do this it will also run EF Migrations to create the tables for standard ASP.Net Identity.  If you return to inspect the database you will find these have been created.

Now the final task is to create the Lynicon roles and add them to the user you have created.  Run the SQL script at /Areas/Lynicon/Admin/SQL/SetUpIdentity.sql against the database, which will create the default roles for Lynicon and make all currently existing users Admins in the CMS.

...

Build the Site

Run a build on the site as the commands you are about to run will load the current site's compiled code in order to enable them to execute, and they won't work without this step.

Build the Database

If you used the default connection string from the project scaffolding which points to an .mdf file in App_Data, you will need to ensure the database is created before running the initialization commands.

Image Added

These initialize and activate Entity Framework Migrations.

• Enable-Migrations: this sets up the project for migrations
• Add-Migration -Name Init: this creates the first migration to create the database with ASP.Net Identity tables set up
• Update-Database: this runs the migration

Run the Initialization Commands

Image Added

Go to the Package Manager console.  Lynicon has installed Powershell commands to set up the CMS.  The commands to run (in this order) are shown in the image.  They are:

• Initialize-LyniconProject: this inserts commands into the Global.asax.cs to run lynicon initialization, and into FilterConfig.cs to set up Lynicon's MVC script manager
• Initialize-LyniconDatabase: this builds the core database tables needed for Lynicon
• Initialize-LyniconAdmin: this creates an admin user for Lynicon with all the admin roles, allowing you to access the CMS editor and back end.  You have to supply a Password parameter ensuring that the admin password is never set to a default value.  Ensure you use single quotes for the password to avoid issues with special characters. The admin user's username is 'administrator' and the default email is 'admin@lynicon-user.com'
  
  

First Run

If you now run the site and log in as the administrator you will be able to see the Lynicon pages as described in the the User Manual.  Lynicon is now ready to be used for CMS functions.

To now set up a basic content-managed model, route and view, consult the the Hello World page.