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
Sisulizer UI works, slmake.exe does not so well - 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 Dec 20th, 2017 02:15 pm
PM Private Upload Quote Reply
olieboer
Member
 

Joined: Tue Dec 19th, 2017
Location:  
Posts: 4
Status: 
Offline
Hello.

We are a long time user of sisulizer, and we find it to be a very useful and easy tool.
I am currently trying to localize a new .net project of ours and everything appeared fine as usual. I am currently trying to automate the localization process to include it in our build process to always have our installers localized.
This is where the problem begins.

I execute on the commandline the following command:

slmake.exe create "[Some path]\Translations.slp"

and  get the following error message:
[Some path]\Iris Studio9.proj" (ResolveReferences;MarkupCompilePass1;MarkupCompilePass2 target) (1) ->
(_CheckForInvalidConfigurationAndPlatform target) ->
  C:\Program Files (x86)\MSBuild.0\bin\Microsoft.Common.CurrentVersion.targets(617,5): error : The OutputPath property is not set for project 'Iris Studio9.proj'.  Please check to make sure that you have specified a valid combination of Configuration and Platform for this project.  Configuration='x86'  Platform='AnyCPU'.  You may be seeing this message because you are trying to build a project without a solution file, and have specified a non-default Configuration or Platform that doesn't exist for this project. [c:\ontwikkeling\medical\iris trunk\medical suite\Application\MedicalSleeve\Iris Studio9.proj]

Two things in particular call my attention:
1. The project name does not really exist. We have a project that is called Iris Studio.csproj, but no Iris Studio9.proj
2. The Configuration as well as Platform are Platform settings. For Configuration i would have expected either Debug, Release or Setup. It seems to me this error is thrown by ms build because sisulizer tells it to use invalid configuration/platform settings.

I am desperate for your help. I have already spent a day and a half on this problem

Thank you in advance

Back To Top PM Private Upload Quote Reply

 Posted: Wed Dec 20th, 2017 08:30 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3043
Status: 
Offline
Have you tried to give the complete (absolute) path for your .slp to make sure SLMake got the write files and paths?

Markus



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

 Posted: Thu Dec 21st, 2017 04:11 am
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1985
Status: 
Offline
The error occurs when SlMake tries to compile a localized XAML file into BAML. Most likely reason is that SlMake cannot find the main assembly file of the project.

Do you use SlMake.exe in the same PC as Sisulizer.exe. If not make sure that you have compiled the VS project before using SlMake.

Do you pass the same .slp as in the case of Sisulizer.exe

If you still get the error you should send use a zip file that Sisulizer creates. SlMake output text shpuld contain a line where is "Please send xxx file to Sisulizer support team". Localte the file and send it as a private upload. Click the Private Upload above button to send it.

Ilkka



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

 Posted: Fri Dec 22nd, 2017 12:50 pm
PM Private Upload Quote Reply
olieboer
Member
 

Joined: Tue Dec 19th, 2017
Location:  
Posts: 4
Status: 
Offline
HI.

Your advice made me investigate some more and I think I did find the cause of the problem.
It seems that when I build the slp file from within the sisulizer application (UI) it creates for every xaml file, a localized baml file in the respective directory in the obj output dir like SelectBatchView.fr.baml and also a SelectBatchView.fr.g.cs. If i remove these and rebuild the project in visual studio and then in sisulizer, all works well.
Now if i remove all those files, rebuild in visual studio and then in slmake.exe, those files are NOT created and the error i posted about earlier occurs. This is also the cause of my original problem that made me investigate this in the first place: The localized user interface of our project is not updated by the build script.
Is there any way i can make slmake create the localized baml files as well?

regards Marvin

Back To Top PM Private Upload Quote Reply

 Posted: Fri Dec 22nd, 2017 02:41 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 1985
Status: 
Offline
Hi Marvin,

Sisulizer.exe and SlMake.exe share the code. XAML compilation on both uses the same code. The reason that you won't get .baml files when using SlMake is that the compilation fails. The reason of that is most likely that SlMake cannot locate one or more assembly files that the XAML files use. In order to find why I need to see the full output of SlMake. Can you send it to me.

If on that output there is a text "Please send xxx file to Sisulizer support team" locate the file and send that too.

Ilkka



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

 Posted: Fri Dec 22nd, 2017 02:45 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3043
Status: 
Offline
Please use the Private Upload button right above this post to send your files privatly and bound to this topic.

Thanks

Markus



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

 Posted: Fri Dec 22nd, 2017 04:18 pm
PM Private Upload Quote Reply
olieboer
Member
 

Joined: Tue Dec 19th, 2017
Location:  
Posts: 4
Status: 
Offline
Well that's the thing.

Before, when i first posted, i did get the output of slmake telling me it had created a .zip file that i could send to you.
But now after investigating and rebuilding the vs solution in all configurations, the ability to run slmake was restored, and that message no longer shows up on the command line.

As of now, the output resource.dll files are created fine. Their modify date and time is consistent with the moment i run my command line.
However, when i look into the resource dll with dotpeek (a decompiler) the new resource.dll does not contain some changes that i made especially to diagnose this problem.

When i look in my obj folder, there is no new .fr.baml file created for the xaml file i am interested in.

The command line i currently run and output thereof is this:


C:\Program Files (x86)\Sisulizer 4>"c:\Program Files (x86)\Sisulizer 4\slmake.exe" create "c:\ontwikkeling\medical\iris trunk\medical suite\translation.slp" -lang:fr -e

´╗┐SlMake version 4.0.369 Copyrights (c) 2005-2017 Sisulizer

Loading file "c:\ontwikkeling\medical\iris trunk\medical suite\translation.slp"

Building source "Medical Suite.sln"
There are new items in the project
There are unused items in the project
There are changed items in the project
Saving file "c:\ontwikkeling\medical\iris trunk\medical suite\translation.slp"


Marvin

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jan 4th, 2018 08:04 am
PM Private Upload Quote Reply
olieboer
Member
 

Joined: Tue Dec 19th, 2017
Location:  
Posts: 4
Status: 
Offline
Hello.

I just found out a thing.
Does sisulizer do something with the environment variable "Configuration"? My batch script set this variable to "Mixed platforms" but to debug I disabled all references to it.
I noticed that when i run the command line from a new command window, the command succeeds and the localized baml files are created.
If i ran the batch script with the Configuration variable set, it failed, so i got to thinking.
My batch script runs from visual studio, and maybe that sets some environment variable that sisulizer uses to communicate with VS. So i cleared all variables.
This however caused other errors (tmp was no longer known) but i tried clearing all of the environment variables that i set myself in my batch script and low and behold. It worked.

So i don't know if you guys are programmers as well but i sure would be interested in which environment variables i could set and which to leave as is.

Back To Top PM Private Upload Quote Reply

 Posted: Thu Jan 4th, 2018 03:26 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 3043
Status: 
Offline
Dear Marvin,

If you use or change environment variables to control your build process in Visual Studio then you need to do this for SLMake as well. Sisulizer SLMake depends on Microsofts build tools. Everything that influences the build tools will influence them if called from SLMake as well.

Markus



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

Current time is 03:01 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Sisulizer UI works, slmake.exe does not so well



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

Sisulizer software localization tool - Three simple steps to localize