Releases: Particular/ServiceControl
1.21.0
1.20.0
1.19.0
As part of this release we had 32 commits which resulted in 8 issues being closed.
Improvement
- #757 Support DTC for SQL Server Multi-Instance Topologies
- #755 Add Advanced Options Screen in the Management Utility
- #744 Simplify the Licensing Logic in Management Utility
- #732 Allow reinstalling an instance to work with the same
data files - #715 Support "NT AUTHORITY\LocalService" in Management Utility
Bug
- #749 Initializing Raygun in the background
- #625 Adding ExposeRavenDB setting can cause service to fail on startup
Where to get it
You can download this release from nuget
1.18.0
As part of this release we had 6 commits which resulted in 3 issues being closed.
Bugs
- #676 License dialog is not refreshed when importing a new license file
- #670 ServiceControl Management Utility license screen gives no feedback when importing a license
- #669 ServiceControl Management Utility license dialog doesn't display the edition
Where to get it
You can download this release from our website
1.17.0
As part of this release we had 47 commits which resulted in 10 issues being closed.
Improvements
- #666 ServiceControl Management Utility improve layout for form error and warning messages
- #719 ServiceControl Management Utility MSMQ unsupported features message is badly worded
- #713 Slider for audit and retention period is not precise
- #712 Better error message format
- #678 Add/Edit instance dialog should auto-scroll to the error fields
- #602 Enable to copy ServiceControl's URI in ServiceControl Management Utility
Bugs
- #738 Password validation fails for some Windows 10 users
- #733 Nested path check fails when the directories are siblings with common prefix
- #730 ServiceControl should depend on MSMQ service when the selected transport is MSMQ
- #665 Dropshadow under tooltips in instance action buttons makes the text hard to read
Where to get it
You can download this release from our website
1.16.0
As part of this release we had 13 commits which resulted in 1 issue being closed.
Bug
- #723 ServiceControl cannot be used through an ARR reverse proxy in ServicePulse
Where to get it
You can download this release from our website
1.15.0
1.14.0
As part of this release we had 19 commits which resulted in 5 issues being closed.
Critical Fixes
#717 User's culture is used to serialize objects sent through the REST API
ServiceControl running under non-English culture might return the json data formatted incorrectly. Running with Turkish culture settings as an example, accessing /api/messages REST api, the rendered json will have message_ıd instead of message_id for that property (notice the different i). This is not limited to any given endpoint and is applied through all the property names.
This impacts users of ServicePulse and ServiceInsight
Bug Fixes
- #716 Powershell cmdlet validation of Timespan is broken
- #707 Unable to start Particular.ServiceControl service after upgrading to 1.13.0
- #629 ServiceControl Management and ServiceControl report different license status
- #403 SagaUpdatedMessage handler can cause lots of concurrency exceptions
Where to get it
You can download this release from our website
1.13.0
As part of this release we had 42 commits which resulted in 3 issues being closed.
Improvements
ServiceControl now has a configurable retention period for resolved and archived error messages.
Prior to this improvement the data was never purged from the embedded database which led to some customers experiencing large database growth over time. It is now also possible to "unarchive" messages that have been archived by mistake if this version of ServiceControl is used in conjunction with ServicePulse 1.5
You can learn more about these improvements by reading the issue #694 and also by reviewing the Archived Message Management documentation
Bugs
Where to get it
You can download this release from our website
1.12.0
As part of this release we had 39 commits which resulted in 5 issues being closed.
Improvements
- #693 Error message forwarding should be a mandatory choice during installation or upgrade
ServiceControl forwards a copy of every error message processed to a secondary error queue designated by the app configuration setting ServiceBus/ErrorLogQueue. If no third party utility is processing messages from the secondary error queue then the forwarding of messages can slowly fill the available storage. A new setting has been introduced to allow this behavior to be turned off. When upgrading to version 1.12 via the ServiceControl Management Utility the upgrade process will prompt to disable this behavior. If an upgrade is being done via the unattended install method or via PowerShell commands then refer to the installation documentation
Bugs
- #704 Update ServiceControl to SQL Server transport v2.2.3 to fix SQL 2008 compatibility
- #699 Endpoint Started message presents date in UTC
- #697 Console log entries which detail log file names are not rendered with date
Where to get it
You can download this release from our website