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: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
Can't build WPF project - 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 24th, 2010 10:26 am
PM Private Upload Quote Reply
rvacaru
Member
 

Joined: Wed Jan 27th, 2010
Location:  
Posts: 46
Status: 
Offline
Here's a simpler project we try to localize.
See attached archive.

Last edited on Thu Jun 24th, 2010 10:26 am by rvacaru

Back To Top PM Private Upload Quote Reply

 Posted: Tue Jun 29th, 2010 08:49 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 148
Status: 
Online
I fixed this bug in build 307. The problem was that localized XAML file that Sisulizer created as different case in one attribute (fontsize vs FontSize). Build 307 fixed this.

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Tue Jun 29th, 2010 08:56 am
PM Private Upload Quote Reply
rvacaru
Member
 

Joined: Wed Jan 27th, 2010
Location:  
Posts: 46
Status: 
Offline
Excellent news ;)

Any advice on the other problem?

(ie. "Cannot add content to object of type 'AMADEE.Wpf.DataAgent.DataAgentDataProvider'....)

Back To Top PM Private Upload Quote Reply

 Posted: Tue Jun 29th, 2010 09:24 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 148
Status: 
Online
I studied another bug file (LicensingDialog.de.zip). You have an XAML file called LicensingDialog.xaml. It contais following line

<da:XPathContentDataProviderSelector x:Key="ProviderSelector">
  <da:SelectProvider Operation="Load" XPath="_(at)_Action[.='CheckActivation']" Provider="{StaticResource CheckProvider}"/>
  <da:SelectProvider Operation="Load" XPath="_(at)_Action[.!='CheckActivation']" Provider="{StaticResource RequestProvider}"/>
</da:XPathContentDataProviderSelector>


XALM referers a class da:SelectProvider is correctly included in the header of XAML. When Sisulizer compiles this it creates MsBuild.project that also correctly refers the assembly that contains the class. However MsBuild fails to compile the above lines. It reports an error:

C:\Support\WPF\tosend\Temp2\LicensingDialog.de.xaml(91,10): error MC3028: Can
not add content to object of type 'xxxxx.Wpf.DataAgent.XPathContentDataProvide
rSelector'. Line 91 Position 10. [C:\Support\WPF\tosend\Temp2\LicensingDialog.proj]


Do you have any idea about this error?

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 26th, 2010 08:56 am
PM Private Upload Quote Reply
rvacaru
Member
 

Joined: Wed Jan 27th, 2010
Location:  
Posts: 46
Status: 
Offline
Sorry for the late answer, I was offline a while.

This is exactly the problem that stops us fully using Sisulizer for localizing our app. I don't really understand why this is occuring :(


Another error we get (also in v307) is

error MC1000: Unknown build error, 'Could not load type 'System.Collections.ObjectModel.ObservableCollection`1' from assembly 'System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'. Line 34 Position 59.'

Is the satellite assembly targeting .NET 2.0 ?? In .NET 4.0 the ObservableCollection is in WindowsBase.dll (AFAIK)

I also get still the lowercasing problem (fontsize, command, etc). Do I need to retranslate the whole project to fix that?

Last edited on Mon Jul 26th, 2010 08:58 am by rvacaru

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 26th, 2010 09:04 am
PM Private Upload Quote Reply
rvacaru
Member
 

Joined: Wed Jan 27th, 2010
Location:  
Posts: 46
Status: 
Offline
error MC3072: The property 'fontsize' does not exist in XML namespace 'http://schemas.microsoft.com/winfx/2006/xaml/presentation'. Line 48 Position 53

I uploaded the output.html as private upload maybe u can take a look...

Last edited on Mon Jul 26th, 2010 10:23 am by rvacaru

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 26th, 2010 09:31 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 148
Status: 
Online
rvacaru wrote: error MC3072: The property 'fontsize' does not exist in XML namespace '[url=http://schemas.microsoft.com/winfx/2006/xaml/presentation'.]http://schemas.microsoft.com/winfx/2006/xaml/presentation'.[/url] Line 48 Position 53
I cound not find your sample any more. Can you send it. I need the original XAML, localized XAML and Sisulizer project file (.slp).

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 26th, 2010 09:34 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 148
Status: 
Online
Never min. I found the sample and I am testing again.

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 26th, 2010 10:03 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 148
Status: 
Online
I checked this case. The bug was fixed but it only applies to new project. If you open an existing SLp that has fontsize instead of FontSize SL does not fix it. We will fix this bug too in the next build.

A workaround is to open SLP into text editor and find "fontsize=" (remember case sensitive) and remove that part in the translation.

<lang id="de" status="2">&lt;Hyperlink command="management:LicensingDialog.ReregisterCommand" fontsize="14" foreground="Blue">Ihre Registrierungsdaten ändern&lt;/Hyperlink></lang>

->

<lang id="de" status="2">&lt;Hyperlink>Ihre Registrierungsdaten ändern&lt;/Hyperlink></lang>

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 26th, 2010 10:25 am
PM Private Upload Quote Reply
rvacaru
Member
 

Joined: Wed Jan 27th, 2010
Location:  
Posts: 46
Status: 
Offline
Great.Thx for that.

I uploaded the full output.html log as private upload. It has all the errors we still get. I will try to create a new project and test (importing the translations from the old one)

Back To Top PM Private Upload Quote Reply

 Posted: Wed Jul 28th, 2010 09:36 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 148
Status: 
Online
I think that I finally solved this bug. I will send you a PM where I give you more instructions how to test it.

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Fri Jul 30th, 2010 09:12 am
PM Private Upload Quote Reply
rvacaru
Member
 

Joined: Wed Jan 27th, 2010
Location:  
Posts: 46
Status: 
Offline
Looks really good now! Only 1 error left:

"error MC3050: Cannot find the type 'local:Fields+Domain+Type'. Note that type names are case sensitive. Line 189 Position 29"

(this being the XAML notation for nested classes in WPF)

I'll upload the files via Private Upload so you can take a look.

Thanks a lot!

Last edited on Mon Aug 2nd, 2010 07:44 am by rvacaru

Back To Top PM Private Upload Quote Reply

 Posted: Sun Aug 8th, 2010 10:29 pm
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 148
Status: 
Online
Thank you for the file. I tried to compile the XAML file and I got the same error message. I got the same error message even on the original XAML file. It seems that project files need something additional lines in order to complile the abive syntax. Can you send me your original .csproj file?

Jaakko

Back To Top PM Private Upload Quote Reply

 Posted: Tue Aug 10th, 2010 08:25 am
PM Private Upload Quote Reply
rvacaru
Member
 

Joined: Wed Jan 27th, 2010
Location:  
Posts: 46
Status: 
Offline
Tried again to compile our latest build and seems to work without any problems. Thanks a lot for your support!

Back To Top PM Private Upload Quote Reply

Current time is 01:56 am  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Can't build WPF project



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