getting things together.

Seems like I always have excuses for not writing, still i urge to get stuff written, archived and stored in some safe place. Lately I have been struggling with some dns servers after move of domain. But everything should be sorted now as it seems.

Silly stuff like thinking that if you move a domain to a new host, they will register it with their own name servers. This seem to not always be the case, and I had to re-register it myself on the name servers that my new host provide. Not sure if it was my old host ( who made it hard or my new host (binero) that didn’t care much about it.

Side effect was that no matter what dns/alias i registered/changed for this domain, it had no effect what so ever and continued to point to an IP on the old host.

Anyhow. Stuff moved, set up in new environment and ready to go again. Now I just need to decide if to create my own site for blogging, or continue using WordPress since I’m lazy. The problem is, all cool stuff i know how to do is in .net. Php is something i left behind a very long time ago. Still. If you work with web, I feel you should do your own stuff. So most likely, Instead of writing, I will code something new that maybe some time gets finished, or I’ll just continue whine about how i never get stuff done ^^.


by chance i was dragged into an Umbraco project at work, I did work with Umbraco before, but it was like 5 years ago and I was not that impressed. The thing that bothers me most is that you build your site through a web interface and not with code first.

But things change and some stuff become availible, or atleast starts to get availible. I’ve tried out the Umbraco 7.4.3 and I must say that i start to feel some potential in it again. So much that I will most likely build a personal site around it.

I hope to get better at writing stuff down as well. I’m going on parental leave for 3 months soon, maybe that will let me sort stuff out when it comes to documentation =)

wow, things changed.

i’m impressed. was really easy to move old content to new place, export + import, who would have known. this kind of magic did not exist last time i set up a new wordpress ^^.

nothing to complain about at all atm. even an importer for tumblr, what is this sorcery.

seriously? again?

setting up a new site, again. don’t know which one this is in order, but at least it’s been a while since last time.

not sure why I’m so fixated with having one place on the internet when I don’t mind changing apartment from time to time, guess I care more about words living among the clouds, than about where I sit my ass down at night.

so might not always be bad to set up a new site, but it is always a pain to try move along your previous posts, if you want to..

i guess it somehow is related to where in life you are at, I’m one of those who started exploring internet very early and also claimed my very own shiny domains by that age. some have persisted through the years and some start to feel, maybe not as much me any more.

but how to scrap an old domain that you used for, i dunno like your life on the internet? I don’t know how many different sites i’m registered with aliases referring to those domains,. what will stop working and can you ever feel secure dropping a domain you used for so long?

i guess there will be some sort of transition time where you try to move everything, but it’s not so uncommon that email is something hard to change regarding accounts..

but yes. moving. a site is a start. so let’s begin.

EPiServer 301-handling

Got some room to breath today, so decided to split a simple 301-handling I did some weeks ago into it’s own project and “put it in the git”. Also made a nuget for it if anyone wants to try it out.

I like nugets, if done correctly they make it very easy and clean to try code if you want to, and I’m trying to make it a natural part of when i package stuff for safekeeping.

So what does this thing do then?

Basic 301-handling for EPiServer 7.5+. Support for Domain-redirects. Based on XML-files to be as simple as possible doing nothing more and nothing less.

If domain-redirects exists, that request will be routed first with persistent relative path.

Routes will catch what EPiServer does not want and send it to controller for checking if it’s a 301, if it is, a permanent redirect will trigger to new place. If not, a 404-exception will be thrown falling back on website configured error-handling.

Drop bin-file in your bin-directory. All is IInitializable modules and will hook onto EPiServer.

Optional configuration, add to appsettings

These are also the default paths if no appsettings exist.
XML should look as follows

I trim surrounding /, as well as ignore lower/uppercase on compare. So not that important.

So what about errorhandling?

To accompany this module I usually redirect to a page in EPiServer. Webconfig as

Then I set a page in EPiServer to answer on /error address. The page someone tried to access can be found in TempData[“originalUrl”].

SVG Fallback with DisplayTemplates in EPiServer Mvc 7.5

The requests about doing stuff with Svg starts to increase and it was time to think about how to handle it. I had probobly 5 different complicated ways to do it and since I’m effective (or lazy) i like it to be easy for me to handle.

So what I landed in was actually a pretty simple concept giving the DisplayTemplates some more responsibility. Think I’m pretty ok with this solution. There are some quirks for the EPiServer Editmode where I have some problems with it handling svg as images. But no time for that today. Doing simple failsafe for that place.

So what I do in my DisplayTemplate is to check if there is any more viewData that i care about in this state. Here i decided to use the cssClass on rendering aswell and now check for an svgModel property. If an svg property is present, I render that as main imagetag and I add the original as a fallback. (Here is also the Editmode workaround atm.)

Having this displaytemplate for my ContentReferences with UiHint.Image, i can now pass and extra ContentReference into it as so properties look like this.

and calling it looks like this

That is about as easy as it gets I think. Then I complete it with a js to take care of the fallback if we don’t have support for svg. Using Modernizr.

EPiServer 7.5 handling extra Routedata using Partial Routing

Querystrings are evil and does not make pretty links. We can agree to this yes? So what you normally do is put up routes that can handle all those quirky bastards and put em where they belong.

As an example I’m going to use a newslistpage with pagination. (I’m lazy so i’ll only write relative urls) /newslist. If i want to target a specific page in the pagination, i would normally set up a route to handle it so i could write /newslist/2 instead of the ugly /newslist/?page=2.

But if you are working with a Cms like EPiServer, the paths are not really known all the time and routing changes. This can be a tricky thing and I’ve seen a lot of people just ignoring it and carry on with querystrings since it’s the easy thing to do.

There is a very easy way to deal with this in EPiServer 7+ and it’s called Partial Routing. I was reading some posts about it on and thought, hey i can use that for simpler things aswell. So here is the implementation to use it for your own “extra” route data.

So what it does it add this extra routing to all pages of type NewsListPage. When resolving it, the routing checks if there are any parts of the routing left unhandled. In my case I’m expecting a possible paginationreference, so i try parse it to an int to see if its data i should bother with.

If it fits, I then add that extra data to the RouteData collection. This will make it easily accessible in the Controller.

So to recap, if there are parts left in the routing after hitting the NewsListPage, we handle it in the Partial Router, add it to the routedata collection and then we can fetch it like it was a querystring/normal route in the controller.

To initialize and attach this Partial Routing to EPiServer, we need to load it. I like to keep it pretty clean so I have a class handling it.

And that should be it. No excuse to use querystrings for simple tasks like this ^^

EPiServer 7.5 Mvc Parsing ContentAreas

So this other day I had to get all values from a Page in EPiServer (7.5+) to send to another service. I’ve done it before in earlier versions and thought there would be no problem. However the new ContentArea breaks the pattern a bit and left me confused. Looping through the pageproperties, you could do a switch on the PropertyDataType enum to see what we were dealing with, but not in case of ContentArea it seems.

The funny thing is that there is no ContentArea in that enum and the ContentArea itself says, by Type, that it’s a LongString? So I try do a check on OriginalType and compare to PropertyContentArea, successfully I can identify the ContentArea property. It’s never fun having to compare types though..

What i need to do now is parse everything that is in that contentarea and get the properties for those items aswell. Don’t know how often you do stuff like this but it’s a rather special case and something that is also pretty tight cached, so should be no worries.

The GetExternalUrl() that i use are extensions to get pretty links, which i want from everything that is a PageReference or a ContentReference. This of course varies what you are using em for. But should give you the basic idea.