Christian Engvall

Add an admin user to database using Litium CLI with the litium-db command.

dotnet litium-db user --file .\Litium.Accelerator.Mvc\appsettings.Development.json  --login agoodusername --password anevenbetterpassword

• By supplying –file the command picks up the connection string for us.
• Don’t forget to change agoodusername and anevenbetterpassword to something else.

Read more about Database management at Litium docs

You see a lot of CultureInfo.CurrentUICulture and CultureInfo.CurrentCulture references in the Accelerator. Those are connected to two channel fields called Language for pages and block and Language for products. Lets have a look at when to use which!

Language for pages and blocks and language for products on a channel

Usage

Language for pages and block sets the value for CultureInfo.CurrentUICulture. Language for products sets the value for CultureInfo.CurrentCulture. This means you can do like this when getting a value for a field that is multiculture for proucts:

var baseProductFieldValue = baseProduct.Fields.GetValue<string>("FieldId", CultureInfo.CurrentCulture);

And for blocks and pages you instead get field values like this:

var pageFieldValue = page.Fields.GetValue<string>("FieldId", CultureInfo.CurrentUICulture);

Conclusion

In the Litium projects I’ve worked these fields mentioned above are almost always pointing to the same language. So it often times won’t make much difference. However, if you only use CultureInfo.CurrentCulture when working with products and CultureInfo.CurrentUICulture when working with pages and blocks you’ll be future proof if an editor decides to change those fields.

To use a Middleware with Litium we can create a startup class that inherits the IOwinStartupConfiguration interface and use it to insert a middleware into the OWIN pipeline.

A middleware is, put simply, a piece of code which can read information about the current request and add information to the response. And it’s a good place to put code that doesn’t really fit into controllers or services where we need to examine every request.

The example below will examine every request that comes into a Litium site. We are looking for a specific querystring and we want to store its value as a cookie. This is a real life example, but it has been modified and simplified.

This is tested with Litium 5 and 7 but probably works in more versions.
For the sake of simplicity this post will not take any project standards into consideration. But feel free to use the comments to suggest changes or improvements.

1. Creating a startup class

Since I’m using a fresh install of the Accelerator for demonstration purposes and not doing this in a customer project I’m just going to put this class in the Litium.Accelerator.Mvc root folder. Your project structure will probably be different depending on your project standards.

Start by adding a new class called Startup.cs and let this class inherit and implement IOwinStartupConfiguration. Then we would have a class that looks like this:

using System;
using Litium.Owin.Lifecycle;
using Owin;

namespace Litium.Accelerator.Mvc
{
    public class Startup : IOwinStartupConfiguration
    {
        public void Configuration(IAppBuilder app)
        {
            throw new NotImplementedException();
        }
    }
}

2. Creating a middleware

Create a new folder in the Litium.Accelerator project called Middleware and create a class called UtmCampaign.cs. Let this class inherit from OwinMiddleWare and implement that abstract class. (You need to install the nuget package Microsoft.Owin).

The UtmCampaign.cs class will now look like this:

using System.Threading.Tasks;
using Microsoft.Owin;

namespace Litium.Accelerator.Middleware
{
    public class UtmCampaign : OwinMiddleware
    {
        public UtmCampaign(OwinMiddleware next) : base(next)
        {
        }

        public override Task Invoke(IOwinContext context)
        {
            throw new System.NotImplementedException();
        }
    }
}

3. Adding logic to the middleware

For this example I want to save the campaign name sent by different ad campaigns into a cookie. (I could then use this value when communicating with other third party services, which I have done for some customers, but we won’t cover that in this tutorial).

The UtmCapaign.cs middleware will now look like this:

using System.Threading.Tasks;
using Microsoft.Owin;

namespace Litium.Accelerator.Middleware
{
    public class UtmCampaign : OwinMiddleware
    {
        private readonly OwinMiddleware _next;

        public UtmCampaign(OwinMiddleware next) : base(next)
        {
            _next = next;
        }

        public override Task Invoke(IOwinContext context)
        {
            if(context.Request.Query != null && string.IsNullOrEmpty(context.Request.Query["utm_campaign"]) == false)
                AppendCookieToResponse(context);

            return _next.Invoke(context);
        }

        private void AppendCookieToResponse(IOwinContext context)
        {
            context.Response.Cookies.Append("Campaign", context.Request.Query["utm_campaign"], new CookieOptions {
                HttpOnly = true,
                Secure = true,
            });
        }
    }
}

4. Adding the middleware to the owin pipline

Lets go back to Startup.cs and add the middleware we just created to the owin pipeline like this:

using Litium.Accelerator.Middleware;
using Litium.Owin.Lifecycle;
using Owin;

namespace Litium.Accelerator.Mvc
{
    public class Startup : IOwinStartupConfiguration
    {
        public void Configuration(IAppBuilder app)
        {
            app.Use<UtmCampaign>();
        }
    }
}

And if I now browse to http://accelerator.localtest.me/?utm_campaign=asdf I can see that my middleware is put to use and has created a cookie for me:

Litium middleware result

5. Other uses of IOwinStartupConfiguration

The IOwinStartupConfiguration class isn’t only to used register your own middlewares. You can also use it to, for example, setup signalR if you want to use that on your Litium site.

You can also use it to configure external login providers such as facebook or Google

There are two folders where Litium stores files. The Files Directory and the Common Files directory. Both contains uploaded images, thumbnails, and search indices etc. But the Common files directory is used in multiserver environments, and it stores information that servers would share.

filesDirectory

You can set these paths in web.config. By default the Accelerator v 7.2.3 has the filesDirectory set to ..\Files. I do not want it in the project folder but somewhere else on my disk. It is up to you where you want to put it. Do not forget to add it to your .gitignore(or exclude it from your version control) if you keep it in the default folder.

Lets change this:

  <filesDirectory value="..\Files" />

To this: D:\filefolders\accelerator

  <filesDirectory value="D:\filefolders\accelerator" />

(Don’t forget to set permissions to allow the site to save files to it)

commonFilesDirectory

To set a commonfilesDirectory you can add it below the filesDirectory in web.config

  <commonFilesDirectory value="\\myserver\filefolders\customer\Files" />

You can read more about these directories at the documentation

Lets take a look at using Papercut as SMTP-server during web site development. We’ll also take a look at StateServer. These tools works for any ASP.NET MVC-project but this post is a continuation of the Installing Litium Accelerator post.

1. Papercut

Papercut will act as an SMTP-server and will display every email sent from the website we are building. This is how the creators of Papercut explain it:

Papercut is a 2-in-1 quick email viewer AND built-in SMTP server (designed to receive messages only). Not only does it not enforce any restrictions how you prepare your email, but it allows you to view the whole email-chilada: body, html, headers, attachment down right down to the naughty raw encoded bits. Papercut can be configured to run on startup and sit quietly (minimized in the tray) only providing a notification when a new message has arrived.

Download and install the latest release of papercut and start it.

Papercut

Now open up web.config of your project and change this:

<smtpServer value="" username="" password="" enableSsl="false" />

To this:

<smtpServer value="127.0.0.1" username="" password="" enableSsl="false" />

Next start your site (mine is accelerator.localtest.me) and log in to Litium. Once logged in go to Settings -> Websites -> Websites. Then edit your site and update the Sender email address to an address of your choice.

Litium - Sender email address

Save the settings and order something from the accelerator and you will see an order confirmation email show up in Papercut.

Litium - Sender email address

2. Using StateServer sessionstate

By default the site is setup to use InProc mode. This is fine, But every time the site gets restarted the sessiondata will be lost and we loose information about the cart for example. If we change this to StateServer we save some time every time we rebuild the project since the cart will be saved in our StateServer instead.

Open web.config and change this:

<sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" />

To this:

<sessionState mode="StateServer" stateConnectionString="tcpip=127.0.0.1:42424" />

Then start the services app and start the ASP.NET State Service.

Services

If you do not you will get this error:

State server error