Migrating from Polecat 4 to Polecat 5 New in 1.16.0
Migrate a .NET application from Polecat 4.x to Polecat 5.x. Every break in the 4 to 5 upgrade shipped in the 4.8.0 minor, and 5.0.0 itself changed no public API, so this covers 4.6.0 through 5.0.0: the JasperFx 2.24 / Weasel 9.16 pin bumps and the new Weasel.Storage dependency, the removed Polecat.CodeGeneration package and [Document] attribute, IDocumentSessionListener.AfterCommitAsync gaining an IChangeSet, Polecat.Subscriptions.IChangeListener replaced by Polecat.IChangeListener with Before and After hooks, IWorkTracker.Operations typed as Weasel.Storage.IStorageOperation, ISerializer's members declared on Weasel.Core.ISerializer, the behaviour changes that still compile (sequential Guid ids, correlation ids from Activity.Current, Patch().Set() honouring EnumStorage, AutoCreate.None honoured, no tenant_id column on single-tenant tables so ForTenant stops filtering, [JsonPropertyName] honoured by LINQ and patching), the in-place strong-typed id column conversion, and what landing on a current 5.x adds (5.30's HybridTextStyle.Phrase removal and the filter-before-token search signatures).
Use when upgrading a Polecat 4.x codebase to 5.x, or when code compiled against 4.7 breaks on 4.8+ with a MissingMethodException or an ambiguous IChangeListener.
Skill details
- Skill name:
polecat-migration-v4-to-v5 - Applies to:
polecat - Tags:
migration,polecat,polecat-5,upgrade,breaking-changes,weasel-storage,listeners,serializer,multi-tenancy,schema - Added in: 1.16.0
- License: Proprietary. Copyright JasperFx Software LLC.