Support forum of the software localization tool Sisulizer


.NET, Delphi, ... - Sisulizer Localization Tool Support Home

Get in contact with the makers of Sisulizer.
Our forum is open for all questions around Sisulizer from customers and prospects.
Don't hesitate to register and ask. The Sisulizer team will answer ASAP.

Search     Help Home Sisulizer Website Download
Search by username
Not logged in - Login | Register 

 Moderated by: Sisusupport, Renate.Reinartz, Markus.Kreisel, Ilkka.Salmenius
New Topic Reply Printer Friendly
Incorrect parameter for ALink - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Mon Jul 2nd, 2018 11:22 am
PM Private Upload Quote Reply
vsaveanu
Member
 

Joined: Fri Jun 29th, 2018
Location:  
Posts: 5
Status: 
Offline
Hi,

We recently purchased an Enterprise license to be able to integrate Sisulizer in the build process of our application. The problem that we encountered is that for one project, for just only one language, the parameters generated by SlMake for al.exe are incorrect. Here is a what gets generated:

/v:5.3.25.0
/out:"D:\B\s\Main\Source\***\bin\de\***.***.***.App.resources.dll" /c:de
/company:"Copyright © *** *** ***"
/copyright:"Copyright © *** *** ***"
/product:"*** *** Control"
/title:"***.***.***.Core.dll"
/fileversion:"*** *** Core"
/productversion:"*** *** Core"
/version:"***.***.***.Core.dll"
/embed: [.....]

What seems to happen is that instead of a proper version the name of the assembly is used. This obviously causes ALlink to fail:

ALINK: error AL1026: The version specified '***.***.***.Core.dll' is invalid

This only happens for DE, for the other languages it works fine and the assemblies are generated correctly

The command we execute is simple "slmake create file.slp". The full output of the build and the archive that is generated to be sent to support will be attached to this post.

Note: The people that translate the resources are using Sisulizer 2, Sisulizer 4 is currently only used on the build agent. So the SLP file is in the version 2 format, if there are differences ...

Thank you.

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 2nd, 2018 12:07 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3150
Status: 
Offline
Hi,
I think this issue might be solved in Sisulizer 3 or 4:
4.0 build 360 April 18, 2016
.NET: If Version number check box in Version type of Resource sheet was not checked and Sisulizer could not read the version from AssemblyInfo.cs the default version (1.0.0.0) was used.----------------3.0 build 338 February 20, 2013.NET: Sisulizer sometimes could not read a correct .NET version from Visual Studio project file.-----------------

If your project was made in Sisulizer 2 it might have read wrong version info. Now this is in your .SLP

Since there had been a lot of changes than above in .NET since Sisulizer 2 it might be a good idea to update these licenses since we can't support Sisulizer 2 anymore.
Anyway we look into your files to see a difference in the German branch of your project. Perhaps there is an easy workaround.

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 2nd, 2018 12:11 pm
PM Private Upload Quote Reply
vsaveanu
Member
 

Joined: Fri Jun 29th, 2018
Location:  
Posts: 5
Status: 
Offline
The version we use on the build agent is 4, but it is using a file that is maintained by people running Sisulizer 2.There are talks to move everyone to the latest version but these things take time.

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 2nd, 2018 12:27 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3150
Status: 
Offline
If your slp from Sisulizer 2 has missing info Sisulizer 4 build server can't overcome that.I asked my colleque to look into your slp if he can identify the missing or wrong info.
Updating to Sisulizer 4 is good idea since .NET development goes on and Sisulizer 2 is a dead end. Around 8 years of improvements...

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 2nd, 2018 01:04 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3835
Status: 
Offline
Hello,
Could you send to us your SLP and source files via Private Upload form? We can't reproduce this issue without those files.Here is article about our upload system: https://www.the-localization-tool.com/tech-support-and-using-our-upload-form/
Best regards,Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 2nd, 2018 01:13 pm
PM Private Upload Quote Reply
vsaveanu
Member
 

Joined: Fri Jun 29th, 2018
Location:  
Posts: 5
Status: 
Offline
I'll need to ask approval for the SLP file.

What "sources" do you need?

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 2nd, 2018 02:17 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3835
Status: 
Offline
If you use .NET project (w.g. based on sln or csproj file) as source in the Sisulizer project, you should send all files belonged to specified .NET project required for correct compiling output assembly dll by Sisulizer and .NET environment. If you use binary localization, sent original assembly file.

Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Tue Jul 3rd, 2018 06:50 am
PM Private Upload Quote Reply
vsaveanu
Member
 

Joined: Fri Jun 29th, 2018
Location:  
Posts: 5
Status: 
Offline
I think I found the problem. I'll upload the SLP file, please check lines 4672 and/or 4684.

Back To Top PM Private Upload Quote Reply

 Posted: Tue Jul 3rd, 2018 10:12 am
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3835
Status: 
Offline
Hmm... They have status set as Unused. Unused items are still in a Sisulizer project, but they should not be used in output files. just in case, open "Project" menu in the Sisulizer and click "Remove Unused Items". Next save project and try build output files.
Janusz



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

 Posted: Thu Jul 5th, 2018 08:56 am
PM Private Upload Quote Reply
vsaveanu
Member
 

Joined: Fri Jun 29th, 2018
Location:  
Posts: 5
Status: 
Offline
I've corrected the offending values and now everything is working fine. Thank you for the help, it is appreciated.

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jul 5th, 2018 09:04 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3150
Status: 
Offline
Thanks for the update!

Markus



____________________
http://www.sisulizer.com - Three simple steps to localize
Back To Top PM Private Upload Quote Reply

Current time is 12:24 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Incorrect parameter for ALink



WowUltra modified by Sisulizer Copyright © 2007-18 by Jim Hale - Based on WowBB Copyright © 2003-2006 Aycan Gulez

Impress - Privacy statement

Sisulizer software localization tool - Three simple steps to localize