The future of Catel

We have been working very hard on creating, improving and supporting Catel the last 6 years. Last week we released another update for Catel (4.5). This is probably going to be the last release in the 4.* versioning range.

Change of focus

One of the spear points for Catel is the (long-term) support for businesses and frameworks. For example, it’s one of the last (feature-rich) frameworks supporting Silverlight.

However, with the usage of Silverlight declining (as it should), we must shift our (valuable and scarce) resources to where our company can benefit the most of Catel.

We haven’t been using the Silverlight / Windows 8.* deployments ourselves for more than 3 years now, and it’s time to let go of the past. Starting with Catel 5.0, we will only be supporting:

  • WPF (4.0 / 4.5 / 4.6)
  • Universal Windows Platform (UWP)
  • .NET Core / PCL
  • Xamarin

This means we are dropping support for:

  • Silverlight 5
  • Windows Phone 8.0 (Silverlight)
  • Windows Phone 8.1 (Silverlight)
  • Windows Phone 8.1 (Runtime)
  • Windows 8.1 (Runtime)

Change of components and breaking changes

Since some technologies come and go, we will also remove support for the following extensions starting with Catel 5.0:

  • Catel.Extensions.CSLA
  • Catel.Extensions.Wcf.Server

We will be introducing a lot of breaking changes in Catel 5.0 as well.

Change of deployment

Until now, we have been publishing prerelease versions of Catel to NuGet. This can lead to a lot of garbage on the NuGet feed though. Starting with version 5.0, we will be deploying unstable packages to a separate MyGet feed:

Note that beta and stable releases will still be available on NuGet.

If you want to use the unstable versions of Catel, please add the MyGet feed to your list of package sources for NuGet.

The road ahead

The road ahead for Catel looks bright. We have no plans to stop development of Catel since it’s a widely used and popular development framework. We will however keep trying to improve and make it as lean as possible to minimize complexity and maintenance costs.

It will however take us some time to develop 5.0, so we ask for your patience. Feel free to follow development though on GitHub.