May 16, 2011

Linx version 2.3.727.1121

Please note that Linx version 2.3.727.1121 is ready for download. Please see the release notes for a complete list of changes. Some of the new features / changes include:
  • HTTPS support for the Linx server. Linx now makes use of a self-signed certificate to encrypt data traffic to and from the server. Note that this feature changes the default address of the Linx server from "http://localhost:8022" to "https://localhost:8022". It is also possible to configure the server to make use of a signed certificate (if desired). For more information, please read the following help file.
  • Simplified user rights on the server. The existing user rights on the server have been consolidated into 3 new rights: ManageSolutions, ManageServices and RunProcesses. Note that existing rights will be converted automatically to these new rights when you do an upgrade. The following table shows a mapping from the old user rights to the new user rights:

    Old RightNew Right

    * All users will be assigned the RunProcesses right when an upgrade is performed.

The next piece of development work (as per the roadmap) will be to convert Linx to run on .NET Framework 4. As always, comments and suggestions are welcome.

May 15, 2011

Visit to Johannesburg

Annu and I visited Johannesburg on Wed and Thu to see some of the Digiata users of Linx and Stadium. We received some great feedback. Here are the main trends for Linx from our visit and the poll we did earlier:

  • Easy to use
  • Can do anything
  • Sizing if UI windows
  • Building WO Model again and again and agai...
  • Debugging limitations especially when calling one process from another
  • Help for components
  • Debug through called processes
  • Higher level view of process interactions
  • Bulk upload component for quickly getting large volumes of data into databases
I have incorporated these and all the other issues we discussed into our roadmap and/or HotHouse. Some issues that were mentioned have already been fixed in newer versions of Linx e.g. the stability of the Linx Client.

Thanks to everybody that participated. If I missed any important points and you cannot find it on the roadmap or in HotHouse, please log it in HotHouse.

May 11, 2011

Upgrading from Linx version 2.2 to 2.3

The change from version 2.2 to 2.3 was mostly a re-branding exercise (Digiata to Twenty57). This entailed:
  • Renaming all namespaces in the Linx code base.
  • Renaming Linx files where applicable, e.g. "Digiata.Linx.EMX.dll" changed to "Twenty57.Linx.EMX.dll".
  • Changing the default installation directory from "C:\Program Files\Digiata Linx" to "C:\Program Files\Twenty57 Linx".

To migrate the Linx program files to the new version, it is highly recommended to uninstall the old version first and then install the new version. Note that it is possible to specify a custom directory during installation, so it is possible to install the new version to the same location where the old version was installed (if desired).

Linx solution files (.lso) that were created in the old version will open automatically in the new version. Please be aware that after saving a solution file in the new version, you won't be able to open it in the old version anymore.

Some additional notes regarding the upgrade:
  • There is a bug in the existing released version of Linx that will prevent you from converting solution files that contain the "DigiataReporting" component. This has been fixed and will form part of the next release. All other components are successfully converted.
  • Some old solution files may display the following error when you open them: "Could not load file or assembly 'EAGetMail, Version=, Culture=neutral, PublicKeyToken=e10a0812eb29cf94' or one of its dependencies". This error is not related to the changes made between 2.2 to 2.3.
    To solve this error, open the relevant .lso file in a text editor, e.g. Notepad and search for:
    EAGetMail.ServerAuthType, EAGetMail, Version=
    Replace this text with (note that the version number has changed from to
    EAGetMail.ServerAuthType, EAGetMail, Version=
    After saving the file, you should be able to open it up in Linx again.

May 10, 2011

What to expect in the next version of Linx

The following list highlights some of the features that you can expect in the upcoming release of Linx. More detailed information will be provided once the actual release is done, but this should help you to prepare your environment (if necessary) and plan ahead in the meantime:
  • The Linx client application will be removed. All management of the server will now be done through the web site.
  • The web service and web server will now run on HTTPS.
  • Overhaul of the user rights on the server. An upgrade path will be provided to migrate from the old rights to the new rights.
  • This will be the last version of Linx to run on .NET Framework 3.5. The next version will run on .NET Framework 4.
Please refer to the roadmap for more information.