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
Support .NET 4.8 - 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: Thu Jun 27th, 2019 12:39 pm
PM Private Upload Quote Reply
martin.buehlmann
Member


Joined: Wed Mar 23rd, 2016
Location: Switzerland
Posts: 28
Status: 
Offline
We had to update our projects to .NET 4.8.

When I run "Scan for changes" in Sisulizer, it finds all new texts, but I cannot create satellite assemblies anymore with slmake.exe.

When I check the .slp file I see that Sisulizer removed the netversion attribute for all assemblies and so slmake.exe is unable to find the .NET framework tools (al.exe).

We have to release our software by end of this week... So I hope to get a fix from you as soon as possible.

Thanks in advance for your help!
Martin

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jun 27th, 2019 12:52 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3281
Status: 
Offline
.NET 4.8 is not tested with Sisulizer by our R&D and thus not supported yet. I don't have any ETA for a new version.

Best regards
Markus



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

 Posted: Thu Jun 27th, 2019 12:57 pm
PM Private Upload Quote Reply
martin.buehlmann
Member


Joined: Wed Mar 23rd, 2016
Location: Switzerland
Posts: 28
Status: 
Offline
I have a painful workaround for this. Our translator has to MANUALLY add the following attribute to all assembly references in the .slp file.
netversion="net472"

Then I am able to point to the correct .NET Framework tools by configuring the path in the .slo file.

It works, but is a real pain. Hope you will release a fixed version soon!

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jun 27th, 2019 01:01 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3281
Status: 
Offline
Dear Martin,
it is not broken - it is just not supported yet :-)
I asked R&D about implementing it.

Markus



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

 Posted: Mon Aug 19th, 2019 05:49 am
PM Private Upload Quote Reply
martin.buehlmann
Member


Joined: Wed Mar 23rd, 2016
Location: Switzerland
Posts: 28
Status: 
Offline
How is the progress on this topic? When can we expect an update supporting the newest .NET Framework?

Back To Top PM Private Upload Quote Reply

 Posted: Mon Aug 19th, 2019 11:25 am
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3281
Status: 
Offline
Sorry, don't have a ETA yet.

Markus



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

Current time is 11:01 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Support .NET 4.8



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