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
WPF .NET 4.6.1 compiler error - 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 May 7th, 2018 07:28 am
PM Private Upload Quote Reply
geser.u@buchi.com
Member
 

Joined: Fri May 4th, 2018
Location:  
Posts: 4
Status: 
Offline
Hello,

I use the newest Sisuzlizer version 4.0 Build 370.
I try to localize a new WPF .net 4.6.1 project. But I got always the same error. For a simple test, I have created a default WPF project based on .net 4.6.1 with the same result.
On the sisulizer pc I have installed VS2017 with the build tools and the sdk 10A.
Also with compiled assemblies (debug and release) the errors are not solved.

09:16:24 Creating localized resource files
09:16:24 Compiling localized resx files
09:16:24 Compiling localized XAML files
09:16:27 Error Following BAML files were not found:
C:\Projects\WpfApp461\WpfApp461\obj\Release\App.de.baml
C:\Projects\WpfApp461\WpfApp461\obj\Release\MainWindow.de.baml
09:16:27 Error Could not compile XAML files.
Microsoft (R) Build Engine version 4.7.2558.0
[Microsoft .NET Framework, version 4.0.30319.42000]
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 07.05.2018 09:16:26.
Project "C:\Projects\WpfApp461\WpfApp461\WpfApp461.proj" on node 1 (Restore;ResolveReferences;MarkupCompilePass1;MarkupCompilePass2 target(s)).
Project file contains ToolsVersion="15.0". This toolset may be unknown or missing, in which case you may be able to resolve this by installing the appropriate version of MSBuild, or the build may have been forced to a particular ToolsVersion for policy reasons. Treating the project as if it had ToolsVersion="4.0". For more information, please see http://go.microsoft.com/fwlink/?LinkId=291333.
C:\Projects\WpfApp461\WpfApp461\WpfApp461.proj : error MSB4057: The target "Restore" does not exist in the project.
Done Building Project "C:\Projects\WpfApp461\WpfApp461\WpfApp461.proj" (Restore;ResolveReferences;MarkupCompilePass1;MarkupCompilePass2 target(s)) -- FAILED.

Build FAILED.

"C:\Projects\WpfApp461\WpfApp461\WpfApp461.proj" (Restore;ResolveReferences;MarkupCompilePass1;MarkupCompilePass2 target) (1) ->
C:\Projects\WpfApp461\WpfApp461\WpfApp461.proj : error MSB4057: The target "Restore" does not exist in the project.

0 Warning(s)
1 Error(s)

Time Elapsed 00:00:00.15

09:16:27 Note Please send "C:\Projects\WpfApp461\WpfApp461\WpfApp461.zip" file to Sisulizer support team.
09:16:27 Writing the German satellite assembly file 'C:\Projects\WpfApp461\WpfApp461\bin\Release\de\WpfApp461.resources.dll'


Thank you in advance

Attachment: 2018-05-07_09h25_05.png (Downloaded 15 times)

Back To Top PM Private Upload Quote Reply

 Posted: Mon May 7th, 2018 12:08 pm
PM Private Upload Quote Reply
Janusz Grzybek
Super Moderator


Joined: Fri Dec 1st, 2006
Location: Zabrze, Poland
Posts: 3826
Status: 
Offline
Hello,

Thank you for files. We'll check this issue.

Best regards,
Janusz



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

 Posted: Mon May 7th, 2018 01:36 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 2005
Status: 
Offline
Restore target could not be found. This indicates that MsBuild cannot call NuGet. Does NuGet work on your Visual Studio?

Ilkka



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

 Posted: Mon May 7th, 2018 02:06 pm
PM Private Upload Quote Reply
geser.u@buchi.com
Member
 

Joined: Fri May 4th, 2018
Location:  
Posts: 4
Status: 
Offline
Hello,

Yes the nuget works fine in Visual Studio.

Best regards,
Urs

Back To Top PM Private Upload Quote Reply

 Posted: Tue May 8th, 2018 02:55 am
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 2005
Status: 
Offline
I tested your file and the building worked fine. There must be something different on your machine. Can you do this

1) Open your project
2) Select Output panel and right click
3) Choose Properties
4) Select Messages and check Detail
5) Build the project. Now Sisulizer writes detailed info to log.

Can you send me the log data

Ilkka

Attachment: Untitled.png (Downloaded 11 times)



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

 Posted: Tue May 8th, 2018 02:23 pm
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 2005
Status: 
Offline
That your for the report. I found out what caused this.

When compiling XAML files Sisulizer needs to use MsBuild of Visual Studio. In your report I saw that MsBuild of .NET framework was used. The reason was that you have 32-bit operating system. Sisulizer did not correctly read the path of VS from system registry if OS was 32-bit. I need to fix this. Unfortunately I don't have 32-bit VM with VS. Can you help me a bit?

Check if you have the following registy key

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\SxS\VS7 and that contains 15.0 key.

If you have go to that directory and check if there is this dir

C:\Program Files\Microsoft Visual Studio17\Professional\MSBuild.0\Bin

If your machine C:\Program Files might be something else and Professional might be Enterprise.

I have attached a similar settings on 64-bit machine.

Ilkka

Attachment: Untitled.png (Downloaded 10 times)



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

 Posted: Tue May 8th, 2018 02:53 pm
PM Private Upload Quote Reply
geser.u@buchi.com
Member
 

Joined: Fri May 4th, 2018
Location:  
Posts: 4
Status: 
Offline
Hello,

The registry key is identically as you have described.

Best regards,
Urs

Attachment: 2018-05-08_16h45_04.png (Downloaded 10 times)

Back To Top PM Private Upload Quote Reply

 Posted: Wed May 9th, 2018 03:55 am
PM Private Upload Quote Reply
Ilkka.Salmenius
Administrator


Joined: Wed Aug 8th, 2007
Location: Tokyo, Japan
Posts: 2005
Status: 
Offline
Thanks. I fixed this. The fix will be in the next build (371). I also sent you a personal message.

Ilkka



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

 Posted: Wed May 9th, 2018 05:45 am
PM Private Upload Quote Reply
geser.u@buchi.com
Member
 

Joined: Fri May 4th, 2018
Location:  
Posts: 4
Status: 
Offline
This fix solves the problem.
Thank you for your fast support.

Best regards
Urs

Back To Top PM Private Upload Quote Reply

Current time is 10:53 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > WPF .NET 4.6.1 compiler error



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