Keep up to date with the Symphony Framework by subscribing to the mailing list.

Check out the new Symphony Framework Academy! It’s the home for information and tutorials to help you get the most from the Symphony Framework! Click on the Academy option below.

Symphony Framework Release Notes

Symphony Framework Version 3.2.20.0.


Change set: 41658


Added the ability to specify a “DSN:data_source_name” mapping criteria for Symphony Harmony. When defined you must define the logical SYMPHONY_CUSTOM_MAPPING_CLASS to point to the required Namespace.Class.Method to call. The method should receive two string arguments – the DSN string and the table name, and should return a string containing the actual file name.

Change set: 41659


Added the ability to specify custom authentication. The custom authorization provides the ability for the client and server to fully authenticate the connection and request using user defined methods. For example the client could authenticate using, for example, a google account login or a windows domain login. This successful login token data can then be sent to the server where custom code can again be used to authenticate the client.
To configure authentication you must provide a library that contains a class that implemented the ISymphonyAuthentcation interface. This interface currently provides for to methods – one to authenticate the connection and a second to authorize the command. The resulting library should be placed in the Symphony Bridge folder and within the configuration file the following setting should be configured: SYMPHONY_AUTHENTICATION_CLASS. The format of this setting is “Namespace.Class, AssemblyName”.

Change set: 41661


Added the ability to call Symphony Bridge through a REST API. The Symphony Bridge server now provides a self-hosted REST server. This initial release provides the ability to perform SQL like commands through a REST syntax.

Change set:41664


A fix has been applied to the FileIO class to prevent fatal errors when assigning an IOHook class when accessing data via xfServer. The FileIO class now correctly assigns the IOHook class on the correct thread on which the file is opened. The Dispose() method of the IOHook class is now correctly executed when a channel is closed.

AppDomain.CurrentDomain.ExitProcess. This event is now attached to and code to shut down the Symphony dispatchers is executed.

A new static method Symphony.Condctor.Static.ThreadSafe.SymphonyShutdown has been provided to allow control and closure of all thread based dispatchers. This call will correctly wind down all dispatchers and allow correct closure of all associated objects. This method should be called when your program is closing (not from within the domain ExitProcess event). Once called there should be no further processing of Symphony logic or File access.

The Symphony Harmony framework has had several performance improvements.