Chris van de Steeg

Sitecore projectstarter 2.1.0 released: habitat support

Chris van de Steeg — Wed, 13 Jul 2016 12:44:57 +0000

Sitecore projectstarter 2.1.0 has been released on nuget and Github. New features are: Support for Sitecore Habitat (!) *.config.transform files are applied to your config files (supported in non-habitat projects also) Include AutoPackageInstaller in your project (if a sitecore package is dropped in a hot folder, your next request will tell you to install this package) …

Continue reading "Sitecore projectstarter 2.1.0 released: habitat support"

Sitecore frontend with .NET Core

Chris van de Steeg — Wed, 08 Jun 2016 11:27:14 +0000

To get myself comfortable with .NET core (or asp.vnext as it was named at that time), I decided to try and create a frontend for the Habitat-demo site by getting data from Sitecore through the Sitecore Client Services api. Though I did by far not implement all features, I got quite far and it sure …

Continue reading "Sitecore frontend with .NET Core"

Extending Sitecore.Services.Client results

Chris van de Steeg — Wed, 01 Jun 2016 11:00:04 +0000

Last year, David Peterson posted an article about Extending the Sitecore Services Client. Though that is the most elegant solution, Sitecore (-Services Client) doesn’t come with dependency injection out of the box. I tried to go the other way around, and modified the results by adding actionfilters. I’d rather see Sitecore modifying their code to …

Continue reading "Extending Sitecore.Services.Client results"

Sitecore composite components

Chris van de Steeg — Tue, 03 Nov 2015 13:55:34 +0000

I think the title says it all, although some call them snippets ;-). Composite components lets you design components in the Sitecore Experience Editor and have those components be placed as a whole on a page. Composite components will appear on a page as readonly in the Experience Editor. Clicking the special header will open …

Continue reading "Sitecore composite components"

Sitecore donut caching: don’t cache those nested placeholders

Chris van de Steeg — Tue, 06 Oct 2015 11:16:10 +0000

When you are using components with nested placeholders (beit normal placeholders or dynamic placeholders), most times you don’t want to cache the output of those placeholders. You want each component in that placeholder to decide for itself if it is cacheable. That’s why I created a nuget package that disables the caching of the nested …

Continue reading "Sitecore donut caching: don’t cache those nested placeholders"

Sitecore projectstarter

Chris van de Steeg — Mon, 14 Sep 2015 15:11:57 +0000

Every now and then I have an idea for Sitecore that I want to try out quickly. Since (even with SIM), it’s quite some work to setup an empty Sitecore environment, I decided to make a nuget solution to quickly start a new Sitecore project. The resulting nuget package is Sitecore Projectstarter (github)Using this package, …

Continue reading "Sitecore projectstarter"

Sitecore codefirst renderings

Chris van de Steeg — Tue, 16 Jun 2015 08:27:58 +0000

One of the boring tasks when configuring a new sitecore website, is that you have to create the renderings for all controller actions you have created. This is the reason I’ve created a new data provider that adds all controller actions (or configurable what controller actions) to sitecore as a controller rendering. If you install …

Continue reading "Sitecore codefirst renderings"

Sitecore Conditional configs 2.0

Chris van de Steeg — Fri, 08 May 2015 09:03:32 +0000

I just pushed an update for conditional configs to nuget and github. This new release contains 3 new features. The first new feature is that you can now set condition-* attributes on any sitecore config file! In the application’s prestart event, the module scans all .config files in /App_Config/Include for a matching condition- attribute. If …

Continue reading "Sitecore Conditional configs 2.0"

Sitecore Conditional configs: deploy just 1 package

Chris van de Steeg — Mon, 06 Oct 2014 20:19:53 +0000

When deploying Sitecore to your DTAP environment, you will always need a separate set of configuration files per environment. One solution to accomplish is this, is to use web.config transforms with slowcheetah. What I personally dislike about this approach, is that you have to create separate builds per environment. That is why we at eFocus …

Continue reading "Sitecore Conditional configs: deploy just 1 package"

Sitecore MVC in a multisite environment: areaâ€™s

Chris van de Steeg — Fri, 13 Jun 2014 12:01:28 +0000

If you are creating a multisite environment using Sitecore & MVC (or any MVC site for that matter), chance is you have to do some weird naming in your controllers to avoid naming conflicts. This is why Microsoft introduced area’s in their implementation of MVC (as did others before them) Using them in Sitecore is …

Continue reading "Sitecore MVC in a multisite environment: areaâ€™s"