Blog posts by josef ottosson

New major version of JOS.ContentSerializer - Version 5.0

Sat, 29 May 2021 09:56:58 GMT

Bug fix and a breaking change in the new major version of JOS.ContentSerializer.

JOS.ContentSerializer now supports TimeSpan? out of the box

Wed, 04 Sep 2019 19:38:02 GMT

Saw the following post today and decided to update JOS.ContentSerializer to support TimeSpan? properties.

The default implementation is really naive:

public object Handle(TimeSpan? value, PropertyInfo property, IContentData contentData)
{
    return value?.ToString();
}

If you want to customize the behaviour, just follow this post

JOS.ContentSerializer now supports TimeSpan? out of the box

Wed, 04 Sep 2019 17:38:02 GMT

Saw the following post today and decided to update JOS.ContentSerializer to support TimeSpan? properties.

The default implementation is really naive:

public object Handle(TimeSpan? value, PropertyInfo property, IContentData contentData)
{
    return value?.ToString();
}

If you want to customize the behaviour, just follow this post

JOS.ContentSerializer now supports TimeSpan? out of the box

Wed, 04 Sep 2019 17:38:02 GMT

Saw the following post today and decided to update JOS.ContentSerializer to support TimeSpan? properties.

The default implementation is really naive:

public object Handle(TimeSpan? value, PropertyInfo property, IContentData contentData)
{
    return value?.ToString();
}

If you want to customize the behaviour, just follow this post

JOS.ContentSerializer now supports TimeSpan? out of the box

Wed, 04 Sep 2019 17:38:02 GMT

Saw the following post today and decided to update JOS.ContentSerializer to support TimeSpan? properties.

The default implementation is really naive:

public object Handle(TimeSpan? value, PropertyInfo property, IContentData contentData)
{
    return value?.ToString();
}

If you want to customize the behaviour, just follow this post

JOS.Epi.ContentApi updated to version 3.0.0

Tue, 05 Jun 2018 14:10:48 GMT

Thanks to the discussion in the comments on the blogpost written by Johan Björnfot I could simplify the code a lot and remove the HttpModule.

Version 3.0.0 is now available on the nuget feed.

It's a major version bump since I removed the HttpModule, you will need to

JOS.Epi.ContentApi updated to version 3.0.0

Tue, 05 Jun 2018 12:10:48 GMT

Thanks to the discussion in the comments on the blogpost written by Johan Björnfot I could simplify the code a lot and remove the HttpModule.

Version 3.0.0 is now available on the nuget feed.

It's a major version bump since I removed the HttpModule, you will need to

JOS.Epi.ContentApi updated to version 3.0.0

Tue, 05 Jun 2018 12:10:48 GMT

Thanks to the discussion in the comments on the blogpost written by Johan Björnfot I could simplify the code a lot and remove the HttpModule.

Version 3.0.0 is now available on the nuget feed.

It's a major version bump since I removed the HttpModule, you will need to

Headless Episerver? Meet JOS.Epi.ContentApi

Fri, 06 Apr 2018 14:29:34 GMT

I read this blog post by Mathias Kunto where he says that he will leave my beloved library behind and start using the new Episerver Headless API instead.

I felt like the picture above :(

I couldn't stand it. So, I decided to create a new library; meet JOS.Epi.ContentApi

Headless Episerver? Meet JOS.Epi.ContentApi

Fri, 06 Apr 2018 12:29:34 GMT

I read this blog post by Mathias Kunto where he says that he will leave my beloved library behind and start using the new Episerver Headless API instead.

I felt like the picture above :(

I couldn't stand it. So, I decided to create a new library; meet JOS.Epi.ContentApi

Headless Episerver? Meet JOS.Epi.ContentApi

Fri, 06 Apr 2018 12:29:34 GMT

I read this blog post by Mathias Kunto where he says that he will leave my beloved library behind and start using the new Episerver Headless API instead.

I felt like the picture above :(

I couldn't stand it. So, I decided to create a new library; meet JOS.Epi.ContentApi

How to configure Episerver to use Active Directory

Wed, 14 Mar 2018 16:33:25 GMT

This is a quick guide showing how to configure Episerver to use Active Directory instead of Multiplexing/WindowsProvider. This is NOT showing how to use Azure AD.
Im testing this on a new Alloy site running Episerver 11.3.1.

NOTE, while this is a quick way of adding Active

How to configure Episerver to use Active Directory

Wed, 14 Mar 2018 15:33:25 GMT

NOTE, while this is a quick way of adding Active

How to configure Episerver to use Active Directory

Wed, 14 Mar 2018 15:33:25 GMT

NOTE, while this is a quick way of adding Active

Customizing PropertyHandlers in JOS.ContentSerializer

Thu, 25 Jan 2018 09:51:43 GMT

Shows how to easily replace a built in PropertyHandler.

Customizing PropertyHandlers in JOS.ContentSerializer

Thu, 25 Jan 2018 08:51:43 GMT

Shows how to easily replace a built in PropertyHandler.

JOS.ContentSerializer 3.0 has been released!

Fri, 29 Dec 2017 18:34:07 GMT

New features

Support for more built in properties

The following properties are now supported out of the box:

BlockData
bool
double
ContentArea
ContentReference
DateTime
IEnumerable<ContentReference>
int
LinkItemCollection
PageReference
PageType
string[]
string SelectOne/SelectMany support.
Url
XhtmlString
NEW IEnumerable<string> ICollection/IList works as well
NEW

JOS.ContentSerializer now supports Episerver 11

Fri, 24 Nov 2017 18:43:31 GMT

I've just pushed version 2.0.0 to the nuget feed.
The following breaking changes was introduced:

Target framework is now set to 4.6.1(same as Epi)
Minimum version 11.1.0 of EPiServer.CMS.UI.Core is required.

I've only tested it with an manually upgraded Alloy

JOS.ContentJson gets replaced by JOS.ContentSerializer

Sun, 21 May 2017 21:09:58 GMT

JOS.ContentJson gets replaced by JOS.ContentSerializer. Fun fun fun!

Custom Episerver routes without querystring - IPartialRouter

Tue, 18 Apr 2017 21:41:48 GMT

I will show you how to easily bind parameters to your action methods without using the querystring.

I have a page, MyPage, with a controller that looks like this:

public async Task<ActionResult> Index(MyPage currentPage, int myId)  
{
    var response = await this.thirdPartyApi.Get(myId);
    // Do something with