Releases: csf-dev/ZPT-Sharp
v2.0.0
This release represents a major rewrite compared to the v1.x code. Some of the core paradigms of the framework have now changed, such as the use of Microsoft.Extensions.DependencyInjection and the alteration of many of the core patterns.
New features
- AngleSharp is now available as a document provider
- Support for
structure
expressions is added - Documentation has been greatly improved
- Numerous other bugfixes and improvements
Breaking changes
There are likely to be too many breaking changes to list. That said, for standard usage the impact on codebases might be self-contained. Some known breaking changes are:
- NuGet package names have all changed. Old packages have been marked deprecated in favour of replacements.
- The way in which the API is invoked has changed completely
- The configuration file is removed
- Support for the legacy XML API is withdrawn
- Support for
load
expressions is withdrawn
v2.0.0-beta.2
Second beta of v2.0.0 rewrite This includes some docs and automation/CI fixes.
v2.0.0-beta.1
First beta release of v2.0.0 rewrite
v2.0.0-issue278test.5
Do not use this release. It was created as a trial whilst working on #278.
v2.0.0-issue278test.4
Do not use this release. It was created as a trial whilst working on #278.
v2.0.0-issue278test.3
Do not use this release. It was created as a trial whilst working on #278.
v2.0.0-issue278test.2
Do not use this release. It was created as a trial whilst working on #278.
v2.0.0-issue278test.1
Do not use this release. It was created as a trial whilst working on #278.
v1.1.0
This is a backwards-compatible feature enhancement release which also contains a few bug fixes. The main headline here is the introduction of a new TALES expression plugin: pipe, which is intended for use as a way of transforming content for rendering in a ZPT document.
Changelog
v1.0.6
This is a bugfix release which resolves a few high-priority issues. It also marks the first release in which the assemblies are strongly-named.
Changelog
- #98 - Use a profiler to determine where performance improvements are available
- #237 - Improve error reporting relating to compilation failures in C# expressions
- #239 - Crash when using a
load:
expression in conjunction with ASP.NET MVC - #246 - Fix build failures
- #244 - Optimise logic by avoiding caching of source info when source annotation is disabled
- #241 - Consolidate versions of dependency libraries
- #238 - Strongly-name all assemblies
- #247 - Fix build errors created by improperly-strong-named assemblies