Archive

As the next version of PostSharp is getting closer to RC, we took the decision to change the version number from 5.1 to 6.0. This decision is purely technical and has no financial impact on customers since our licensing is not bound to the version number.

PostSharp respects semantic versioning, which means that we promise not to do breaking changes within the same major version. Since we had to introduce breaking changes, we had to increase the major version too. This seems fair, since PostSharp 6.0 is the biggest refactoring of our compiler internals in 8 years because we now run natively on .NET Core (PostSharp is now essentially a .NET Standard component). The good news are that there are almost breaking change at source code level, so, most probably, all you have to do is to update your packages.

We also decided to take the "PostSharp versioning hell" problem seriously, so you will now be able to reference several versions of PostSharp in the same solution. We've developed an internal tool that verifies the compatibility of our APIs with the previous version, including some details like serializable types and shared internals. 

Happy PostSharping!

TL;DR If you use .NET Standard or .NET Core, you must now upgrade to PostSharp 5.1 even if it is not RTM.

We’re happy to announce that the first preview of PostSharp 5.1 is now ready for download on NuGet Gallery (make sure to enable the “include pre-release” option) and on our website.

PostSharp 5.1 will focus on providing support for .NET Standard 2.0 and .NET Core 2.0. Our objective is to port the PostSharp compiler itself to .NET Standard 2.0 so that we can compile .NET Standard and .NET Core applications natively, without cross-compilation. PostSharp 5.1 will still only support Windows as the only build platform.

PostSharp 5.1 comes after months of increasing instability of PostSharp 5.0. Initially, we tried to implement support for .NET Standard 2.0 and .NET Core 2.0 as bug fixes on the top of PostSharp 5.0, but it proved impossible to do without a significant refactoring of our type binding logic. We decided that, in respect to our .NET Framework users, we could not afford to destabilize PostSharp 5.0 any more, and therefore that any effort to support .NET Standard and .NET Core would go into a new version.

For the same reason, we will no longer solve bugs in .NET Standard 1.* and .NET Core 1.* in our PostSharp 5.0, but only in PostSharp 5.1.

PostSharp 5.0 was significantly destabilized by the release of .NET 4.7.1 and VS 15.5. We did not anticipate the breaking changes, as Microsoft seemed to be more careful with that in the past. At this moment, we realized we passed the breaking point of our type binding component and needed a complete refactoring to isolate us from what Microsoft may deem as implementation details.

We understand that several customers are not allowed to use pre-RTM releases of a product and our decision may push them in a difficult situation. We sincerely apologize. We’re going to push hard to move PostSharp 5.1 to RTM quality as soon as possible. Currently, we consider PostSharp 5.1 to be more stable than PostSharp 5.0, but it lacks testing in the field and customer feedback.

Happy PostSharping!

-gael

We’re excited to announce that PostSharp 5.0 RTM is out and ready for download on Visual Studio Gallery and NuGet. The long awaited new version adds support for .NET Core 1.1, Visual Studio 2017 and C# 7.0. It also introduces brand new features like the OnInvokeAsync advise, the [Cache] aspect, or the [Command] and [DependencyProperty] aspects for XAML applications. And the Logging feature has been completely revamped, now fully customizable and faster than ever.

As in any major version, PostSharp 5.0 is the opportunity for us to do some clean up at the cost of a few breaking changes. We’re also updating our product line, renaming products and regrouping features differently. The most disruptive change will affect PostSharp Express users.

New Platforms

Visual Studio 2017 – We support the new MSBuild project format, side-by-side installations of VS, lightweight solution loads, and achieved significant performance improvements.

C# 7.0 – We tested and fixed all aspects with the new features of C# 7.0, including value-typed tasks and multiple return values.

.NET Core 1.1 – You can now build applications that run on .NET Core 1.1, but you can still only build and debug them on a Windows machine running Visual Studio. Support for .NET Core is a long-term project and you will see gradual improvements in future versions.

.NET Standard 1.3 – Support for .NET Core is achieved through .NET Standard, so you can use PostSharp in your own .NET Standard class libraries.

New Features

Async support in aspects – We’ve closed the gaps in the support for async methods in aspects OnMethodBoundary, so ReturnValue and FlowBehavior are now properly supported. In MethodInterceptionAspect, we’ve added an advice method OnInvokeAsync to handle async methods.

Caching – We've added a brand new ready-made caching framework, which includes not only a caching aspect, but also a cache invalidation aspect. PostSharp Caching 5.0 comes with support for MemoryCache and Redis. See Caching reference documentation for details.

Logging – That's a complete rewrite! The new PostSharp Logging is fully customizable and faster than ever. See Logging reference documentation for details.

XAML – If you're writing XAML applications, you probably wrote a lot of boilerplate code for commands and dependency properties. We've created new aspects to automate that. See XAML reference documentation for details.

Code Contracts – It is now possible to add code contracts to return values and out or ref parameters. The values are validated when the method succeeds.

Architecture Framework – We’re adding NamingConventionAttribute, ParameterValueConstraint  and  ReferenceConstraint.

Deprecated Platforms

Windows Phone, WinRT, Silverlight – These platforms have never got any traction among PostSharp users and we will no longer support them.

Portable Class Libraries – An evil that’s no longer necessary. We’re glad to deprecate them too.

Xamarin – We still believe in Xamarin but had to make choices to reach the 5.0 finish line. We chose to suspend support for Xamarin. Our intention is to get back to work on this platform, but to support it through .NET Standard.

Changes in the Product Line and Licensing

In PostSharp 5.0, we’re reshaping our product line:

  • PostSharp Professional becomes PostSharp Framework and now includes everything you need to automate the implementation or validation of your own patterns, including the Architecture Framework which used to be a part of PostSharp Ultimate. However, PostSharp Diagnostics is removed. PostSharp Professional customers will be offered a free subscription to PostSharp Diagnostics for the whole duration of their PostSharp Professional subscription that has already been paid for. Please contact our sales team if you’re interested. Support for the license server is also removed. Please contact us if you’re impacted.
  • PostSharp Ultimate now has a big brother named PostSharp Enterprise. PostSharp Ultimate will still be an “all you can eat” version: the difference is that PostSharp Enterprise will address the typical non-technical requirements of large companies, namely custom license agreement, on-premises license server, and blueprint source code license. Please contact us if you have a PostSharp Ultimate license and are using the license server.
  • PostSharp Model becomes PostSharp XAML, the must-have companion to your XAML development. Besides NotifyPropertyChanged, undo/redo and code contracts, we’re adding command and dependency property aspects.
  • PostSharp Diagnostics now has a free edition named PostSharp Diagnostics Developer Edition and no longer has any project size limitation. It means you can now add logging to your whole solution for free. There is however a time limitation: your applications will stop logging one day after they have been built. If you need logging, you have to rebuild them. That’s why we call it the Developer Edition.
  • PostSharp Express is renamed PostSharp Essentials. PostSharp Essentials is a free but limited edition of PostSharp. You can use all the features of PostSharp Ultimate, but the number of enhanced classes is limited to 10 per project or 50 per solution as in PostSharp 4.3. Additionally, it includes the time-limited PostSharp Diagnostics Developer Edition. We have removed the licensing mode that enabled for backward compatibility with PostSharp 2.0-4.2.

The next table summarizes the licensing changes:

New Product

Previous Product

Changes

PostSharp Enterprise

PostSharp Ultimate

Tiered licensing, min. 50 licenses.

More enterprise licensing options.

Source code blueprint license added.

PostSharp Ultimate

PostSharp Ultimate

Support for the license server removed.

PostSharp Framework

PostSharp Professional

PostSharp Diagnostics removed.

PostSharp Achitecture Framework added.

PostSharp Essentials

PostSharp Express

Backward-compatibility mode with PostSharp 4.2 licensing removed.

PostSharp Diagnostics Developer Edition added.

PostSharp Diagnostics

PostSharp Diagnostics

Tiered licensing.

Totally revamped product.

Code contracts added.

PostSharp XAML

PostSharp Model

Command and dependency properties added.

PostSharp Threading

PostSharp Threading

Code contracts added.

 

So you’re now asking money for a feature that used to be free?

We hate Orwellian language just as you do. Yes. We’re removing free features from PostSharp Express. We have decided to move from a licensing concept based on feature limitations to a concept based on scale limitations. We have made a first step in August 2016 with PostSharp 4.3, but since it was a minor release, we did not want to break backward compatibility. Therefore, we still included (but did not document) a backward-compatible licensing mode in PostSharp 4.3. We’re now removing this mode. PostSharp 5.0 works exactly as PostSharp 4.3 was advertised to work, minus the backward compatibility with PostSharp 2.0-4.2.

What if you’ve been using PostSharp Express for a long time and you don’t fit within the limitations of PostSharp Essentials? I understand you wish to continue the same features for free in PostSharp 5.0 and may feel pushed into the corner by the new licensing model. You have several options:

  1. Do not upgrade to PostSharp 5.0. Remember that all PostSharp licenses, except evaluation licenses, are perpetual. We are not withdrawing your right to use any prior version of PostSharp. Staying with PostSharp 4.3 may be a perfectly viable option, but remember we will not implement support for new versions of frameworks, languages, or Visual Studio.
  2. Remove PostSharp from your project: use a competitor product or rewrite the boilerplate manually.
  3. Purchase a commercial edition of PostSharp 5.0.

I’m sure there is going to be some emotions out there, and we’re likely to see some angry reactions on social media. But I’m also convinced the best service we can render to the community of PostSharp users is to build a healthy, forward-looking, prosperous company, which implies to discontinue business models that have proved unsuccessful. Our decision will perhaps be unpopular, but this is a healthy, data-based one.

Summary

PostSharp 5.0 is a major release, adding support for .NET Core, Visual Studio 2017, C# 7.0, and introducing exciting new features such as a fully new logging framework, much improved support for async methods, a caching aspect, command and dependency property aspects, and much more.

We couldn’t have implemented all these new functionalities without doing a few breaking changes, which I suggest you double check before you upgrade.

PostSharp 5.0 is also the opportunity for us to reshape our product line. We’ve renamed our products, sharpened their positioning, and moved the boundaries between them. Most commercial customers will not be affected, but if you think you are losing functionalities because of these changes, please contact us to find a solution.

Happy PostSharping!

-gael