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
ALINK ERROR AL1028 - 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: Wed Aug 28th, 2019 12:53 pm
PM Private Upload Quote Reply
MVU
Member
 

Joined: Tue Jul 16th, 2019
Location: Belgium
Posts: 10
Status: 
Offline
Hi, when building my project, I have indicated a public key .snk. Unfortunately, this is not enough. It requires a private key as well. The normal procedure is to send my new DLLs to the software editor who would sign them with their private key. And send me back the DLLs. The problem is that I cannot send him my DLLs because the building process is not complete. It is kind of we are going around in circle. Is there a workaround for this situation ?

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 28th, 2019 01:01 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3297
Status: 
Offline
Does you editor have a license so he can build the DLL for you?

Markus



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

 Posted: Wed Aug 28th, 2019 01:04 pm
PM Private Upload Quote Reply
MVU
Member
 

Joined: Tue Jul 16th, 2019
Location: Belgium
Posts: 10
Status: 
Offline
He has a private snk key but for obvious reasons, he cannot make it available to public (me in this case).

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 28th, 2019 01:15 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3297
Status: 
Offline
The workflow is, that the software developer builds and signs the final binaries. I think there should be only one place where the binaries are signed.

Sounds like you are doing it the other way and run into issues.

My hint is to have the developer build the software and finally also sign it.

Markus



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

 Posted: Wed Aug 28th, 2019 01:22 pm
PM Private Upload Quote Reply
MVU
Member
 

Joined: Tue Jul 16th, 2019
Location: Belgium
Posts: 10
Status: 
Offline
Unfortunately that will not be possible. They do not have Sisulizer. They told me that I could (or should) have localized updating the RESX files. But doing so is tedious. Working with sisulizer is much more efficient and faster. Also, by editing RESX files, I would have to carry out some work in Visual Studio etc. Something I am not familiar with. I am quite disappointed. Not by sisulizer, but by the situation I am stuck in right now.

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 28th, 2019 01:35 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3297
Status: 
Offline
Hi,
I understand. But the process of signing has to make sure that only the key owner is allowed to sign. Can't you exchange binaries without signing and they only sign the final version in Visual Studio?
Markus



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

 Posted: Wed Aug 28th, 2019 02:55 pm
PM Private Upload Quote Reply
santra
Member
 

Joined: Thu Jun 2nd, 2016
Location:  
Posts: 6
Status: 
Offline
If you use public key they AL.exe can only delay sign. This is what you should do. Did you remember to specify /delaysign parameter for AL.exe

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 28th, 2019 03:05 pm
PM Private Upload Quote Reply
MVU
Member
 

Joined: Tue Jul 16th, 2019
Location: Belgium
Posts: 10
Status: 
Offline
How do I specify delay sign parameter for AL.exe ?

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 28th, 2019 03:36 pm
PM Private Upload Quote Reply
santra
Member
 

Joined: Thu Jun 2nd, 2016
Location:  
Posts: 6
Status: 
Offline
I guess you use binary localization where you have selected .dll or .exe into Sisulizer. Right click that file in the project file and choose Properties. then follow this screenshot.

Attachment: Sign.png (Downloaded 9 times)

Back To Top PM Private Upload Quote Reply

 Posted: Wed Aug 28th, 2019 04:07 pm
PM Private Upload Quote Reply
MVU
Member
 

Joined: Tue Jul 16th, 2019
Location: Belgium
Posts: 10
Status: 
Offline
It looks promising. I just built the project and have sent the DLL's to the editoir for signing with his private key. I cross the fingers. And will update you.

Back To Top PM Private Upload Quote Reply

 Posted: Fri Aug 30th, 2019 06:37 am
PM Private Upload Quote Reply
MVU
Member
 

Joined: Tue Jul 16th, 2019
Location: Belgium
Posts: 10
Status: 
Offline
It works just fine ! Thanks a lot !

Back To Top PM Private Upload Quote Reply

Current time is 12:52 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > ALINK ERROR AL1028



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