What's New in PostSharp 6.7
PostSharp 6.7 brings the following improvements:
- Support for Xamarin and Blazor
- End of Support for .NET Framework 4.0 and Visual Studio 2015
- Logging: better integration with existing logging frameworks
- Better support for async iterators
- Telemetry: reporting of performance issues
- No registration needed
PostSharp 6.7 removes support for .NET Framework 4.0 and Visual Studio 2015, and has several other minor breaking changes. See Breaking Changes in PostSharp 6.7 for details.
We have revamped our test suite and we can now confidently say that we are supporting Xamarin and Blazor (both client- and server-side) as run-time platforms, but still only through .NET Standard.
That means that you can now add supported PostSharp packages to your .NET Standard libraries and then reference these libraries in your Xamarin or Blazor application project. Adding PostSharp directly to a Xamarin or Blazor application project is not supported. For details, see Compatibility with Xamarin and Compatibility with Blazor.
We're sorry-not-sorry to say goodbye to .NET Framework 4.0, released in March 2010 and supported by Microsoft until January 2016. The oldest supported version of .NET Framework becomes 4.5.0.
Our telemetry shows that a couple of percent of users are still targeting .NET Framework 4.0. However, we have taken this decision to allow ourselves to move forward with our build and test pipeline, since recent frameworks no longer support old platforms.
Consistently with our support policies, we are also retiring support for Visual Studio 2015. Microsoft has ceased to provide mainstream support for Visual Studio 2015 in October 2020.
For users who cannot update their development environment, we recommend to stay with PostSharp 6.5, our latest Long-Term Support version.
We're introducing two features to make it easier to use PostSharp Logging with existing logging frameworks:
PostSharp Logging can now collect log records coming from hand-written logging code and redirect them into its own pipeline. For details, see Collecting Logs from Other Frameworks.
PostSharp Logging can now write its output to several target frameworks instead of just one. For details, see Multiplexing Log Output to Several Frameworks.
We are now detecting when PostSharp Tools for Visual Studio blocks the UI thread and, with your permission, we will report these situations to our online telemetry service. We have also improved the user experience for exception reports.
We are no longer asking your email address to start with the trial or with PostSharp Community.