Technical overview

This page gives an overview of the different techologies used in Entity CMS and Entity Commerce

We all love lists, so let's cut straight to it:


Core framework

Main technologies and libraries.

  • .NET Framework 4.8
  • SQL Server 2019
  • Web API 2.x
  • Entity Framework 6.x
  • ASP.NET/C#
  • Lucene Search Engine
  • JWT Tokens for authorization
  • Internet Information Services

Integrations and third party libraries

Some integrations and third party libraries that are included, and used by different modules.

  • Google Analytics/Google Tag Manager
  • Google eCommerce Tracking
  • PayPal
  • PayEx
  • Stripe
  • EPPlus Excel import/export
  • SendGrid
  • ImageShop media library
  • Campaign Monitor API
  • Link Mobility SMS Gateway
  • Select PDF - PDF/image generator
  • QR Codes
  • Nets/netaxept/vipps
  • Visma

Developement environment

  • Visual Studio 2019 with full Intellisense(TM)

Summary

The different technologies used allows you to deliver both headless and traditional websites, and even hybrid solutions when needed. We strive to stay close to the industry standards, so all .NET developers will be able to work efficient from day one, and to keep the upgrade paths as straight forward as possible. By including specialized third party libraries, we can focus on our primary goals, yet give the clients best in class solutions.


The road ahead

We are currently using Bootstrap 4 as the default responsive framework. There is a version 5 in preview as of autumn 2020, and we will upgrade the current templates to this version when it is stable.

With the new version of .NET coming in late 2020, we will make some breaking changes to the rendering engine to use Razor Pages. These changes will not happen until 2021, and will only affect new installations and upgrades.

With the change to Razor Pages together with headless design, there also opens up possibilites to take advantage of Blazor to give rich experiences for Mobile Apps. We will be exploring these roads as the techology matures.

As for the general functions and features roadmap, we have an agile approach to this. This means that we are constantly evaluating the current state and add or expand the modules as the customer needs and the web are constantly changing.