Selected Customers

Specials run until 6/10/2020

Offers are for commercial and industrial customers only.
All prices are net.

Complete Price Sheet.

Not sure which edition is the right one? Visit our Edition Comparison

Update to Version 4

Sisulizer version 4 is a paid update recommended for all Sisulizer customers.

Update to Sisulizer 4

Still using Sisulizer 3 or Sisulizer 1.x/2008/2010?

Time to update to version 4 now and profit from all new features in version 4.

Software Localization News

Version 4 Build 374 released


The new build comes with many new features. [...]



Tutorials updated [...]

.NET Support updated


New in May 2018: [...]

Sisulizer 4 Build 366


Build 366 - support for Visual Studio 2017 [...]

10 Years Sisulizer


Celebrate and save Big. [...]

Our customers use Sisulizer...

to reach international customers with software in their language

to localize their in-house software in the international subsidiaries

to build multilingual custom software for their clients' enterprises

as Localization Service Providers because it is the localization tool of their customers

to localize software at Government Agencies

To teach software localization at Universities

for software localization on Electronic Devices

To translate software for Biomedical Hardware

to localize software in the Mining Industry

to create multilingual software for Mechanical Engineering


.NET Assembly Version

Every assembly file in .NET has a version number. If the assembly is strong name signed then the version number gets really important because the version number of the satellite assembly must match the version number of the main assembly. How to make sure that the version match. In most cases Sisulizer makes this fully automatic. First Sisulizer tries to read the version number of the main assembly from AssemblyInfo.cs. If that cannot be done then Sisulizer reads the version from the main assembly itself. If the main assembly has a satellite contract attribute then Sisulizer tries to read that and if succesfull uses that instead of the version of the main assembly. If all these fail you have to manually set the version number. Open source dialog.

Check WIN32 resources and check Version number in Version types. Next time you scan the source code version rows will be added. "Versions.1.Assembly Version" specifies the assembly version and you can set it to any value.


Read more about .NET localization.