In the previous article, we set up a base, empty Kentico MVC site, hotfixed it, and installed various tools that we will be using to build the actual website. In this article, we will finish configuring the MVC Site, and add in base elements that all MVC websites have.  This article documents the open source Kentico 12 Baseline repository.

Many may be wondering what I have been up to the past couple months, my blog posts have dried up and the elusive Part 2 of the Build a Kentico site in 24 hours has yet to appear.  Sadly, this is not Part 2 of that blog series, but I do want to give an update on what is all been happening and what activity has occurred.

Building Sites in MVC can be a daunting task.  Many expect it to take double or more time than a normal portal engine site, however with new tools and helpful systems, I plan on showing you how you can build a simple MVC site, using Kentico, in under 24 hours.

This first part covers the first 4 hours of the build: Getting your environment set up, your Kentico site installed, and your tools installed and configured.

THIS POST IS OUDATED, PLEASE SEE NOVEMBER 2019

MVC Routing operates on the basis that a request is handled by Controllers and Actions in predefined routes. Dynamic Routing is where a request maps to a Page (TreeNode), and that Page's settings (Template, Page Type) determines how the request should be handled (which Controller/Action/View). In Portal Engine, the Url matched the NodeAliasPath or Url Aliases of a page, and the Page's Template then determined how it was handled. In this article we will outline how to restore the Portal Engine request handling now that the Kentico 12Service Pack is out.

One of the things I’m known in the Kentico community is my desire to build useful tools for developers, so they can leverage Kentico’s features to a greater degree of ease and scope.  In this article I'll demonstrate a new Module I've created to allow you to more easily create and manage relationships within Kentico.

The future is coming, and those who don't adapt often are left in the dust.  Being future-minded in your development of websites can mean the difference between being able to leverage new technologies and trends, or being faced with a total rebuild, which no one wants.
In this article, I’m going to go over some great principles for structuring your content and relationships to make sure it's ready for whatever gets thrown at it.
 

Thinking of upgrading to Kentico 11?  Wondering how different it will be, what things you might encounter upon the upgrade? Well let’s look at some things, both well known and not so well known that you may find as you work.
 

In any Site or Entity, there are Many-to-One or Many-to-Many relationships.  Whether it be something as simple as “Multiple Banners to display on this page” to the more complex relationships that are needed to do custom ups (such as “Multiple states this dealer serves”).  The tricky part is, there are multiple ways to handle multiple relationships in Kentico, each with pros and cons.  By the end of this article however, you should be able to know which is the best thing for the situation!

Many are familiar with the phrase “Death by a thousand cuts.”  It carries with it the idea that you can do a lot of damage with a sum of seemingly minor things.  This isn’t going to be a tutorial, but more of a warning with other developers on the dangers of taking shortcuts, and breaking Kentico with your code.

Tools tools tools, everyone loves tools!  Tools help you build stuff, do stuff, and better tools mean you can do more with less time and less hassle.  Well, I finally got around to publishing some new tools for you to help you develop your sites.  In this article, I’m going to go through the new tools, explaining my thought processes behind them, along with some great application examples.