Support ScheduledTask control and persistent logs
This commit is contained in:
@@ -1,6 +1,20 @@
|
||||
|
||||
# Changelog
|
||||
|
||||
## [2.3.0] - 2026-08-26
|
||||
### Added
|
||||
- Process-local, assembly-identity-checked resolution and preflight for ScheduledTask `scheduler:` receive locations, including automatic BizTalk/adapter directory and registry discovery plus an explicit configuration override.
|
||||
- Persistent Operation Log grid restoration from retained plain and GZip-compressed daily logs.
|
||||
- **Log Folder** action and a dedicated PROD validation/support runbook in Markdown and plain text.
|
||||
- Regression coverage for Scheduler plan metadata, assembly identity rejection, restart persistence, compression, 30-day retention and detailed exception diagnostics.
|
||||
|
||||
### Changed
|
||||
- Runtime logs now retain 30 calendar days and compress completed daily files instead of deleting everything older than five days.
|
||||
- Grid, result JSON and file logs now preserve exception type, HRESULT, inner exceptions, Fusion loader details and stack traces for support analysis.
|
||||
|
||||
### Fixed
|
||||
- ScheduledTask 7.0.2 receive locations can resolve `Microsoft.BizTalk.Scheduler.dll` from the installed BizTalk environment before WMI `Enable`/`Disable`, without requiring the management tool to mutate the GAC.
|
||||
|
||||
## [2.2.4] - 2026-08-24
|
||||
### Fixed
|
||||
- Permission, Windows Script Host, validation and rollback errors affecting the optional all-users desktop shortcut no longer abort installation, update or uninstallation.
|
||||
|
||||
Reference in New Issue
Block a user