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 
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > VS2010 Silverlight 4 - errors during build

 Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius
New Topic Reply Printer Friendly
VS2010 Silverlight 4 - errors during build - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support
AuthorPost
 Posted: Fri Jul 9th, 2010 12:18 pm
PM Private Upload Quote Reply
dbush
Member
 

Joined: Tue Apr 1st, 2008
Location: London, United Kingdom
Posts: 12
Status: 
Offline
 Hi,

I am trying to get started with localizing Silverlight 4 applications using the Converter example. I have converted the solution to Visual Studio 2010 and changed the project properties to target Silverlight version 4.

I was able to scan the solution and build some translations but when I build I get some errors like the following:


Build FAILED.

"C:\Users\dbush.000\Documents\Sisulizer 2010\Net\Silverlight\Converter\Page.proj" (ResolveReferences;MarkupCompilePass1;MarkupCompilePass2 target) (1) ->
(MarkupCompilePass1 target) ->
C:\Windows\Microsoft.NET\Framework\v2.0.50727\Microsoft.WinFX.targets(317,9): error MC6000: Project file must include the .NET Framework assembly 'WindowsBase, PresentationFramework' in the reference list. [C:\Users\dbush.000\Documents\Sisulizer 2010\Net\Silverlight\Converter\Page.proj]

0 Warning(s)
1 Error(s)


It is not clear to me what this error means; how do I add "WindowsBase, PresentationFramework" into the reference list?

Thanks for any help.

Regards,
Dom.
Back To Top PM Private Upload Quote Reply

 Posted: Fri Jul 9th, 2010 12:27 pm
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
 Can you zip your Sisulizer project file (.slp) and your Silverlight fiel (.xap) into a zip file and upload it to use. Click Private Upload to upload it.

Jaakko
Back To Top PM Private Upload Quote Reply

 Posted: Fri Jul 9th, 2010 01:01 pm
PM Private Upload Quote Reply
dbush
Member
 

Joined: Tue Apr 1st, 2008
Location: London, United Kingdom
Posts: 12
Status: 
Offline
 Thanks for your reply Jaakko. I have just uploaded the files.

Regards,
Dom.
Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 12th, 2010 01:49 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
 Thank you for the files. Your zip contained .sln file instead of .slp. Can you send .slp (Sisulizer project file), please.

Jaakko
Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 12th, 2010 05:38 am
PM Private Upload Quote Reply
Jaakko.Nieminen
Administrator
 

Joined: Sat Mar 20th, 2010
Location:  
Posts: 657
Status: 
Offline
 It seems that you had added Visual Studio project file (.csproj) or solution file (.sln) into Sisulizer. This cause the error. The current Sisulizer build can localize only Silverlight assembly files (.dll) or Silverlight package files (.xap). Sisulizer lets you add VS project file and it correctly scans it but fails to compile localized satellite assembly file.

I fixed this in build 307. Now Sisulizer can corrrectly compile satellite assembly files even you have added a VS project file instead of assembly or package file.

307 will come out soon.

Jaakko
Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 12th, 2010 04:05 pm
PM Private Upload Quote Reply
dbush
Member
 

Joined: Tue Apr 1st, 2008
Location: London, United Kingdom
Posts: 12
Status: 
Offline
 Hi Jaakko,

Thanks for the reply. That is exactly what I did; I assumed that as I could add the .sln file to the Sisulizer project, that was the correct thing to do. I understand that with the version that I have I should directly add the .dll or .xap files.

Can you give me a ball park timescale for when 307 will ship?

Regards,
Dom.
Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 12th, 2010 04:12 pm
PM Private Upload Quote Reply
Markus.Kreisel
Administrator


Joined: Sat Apr 8th, 2006
Location: Monschau, Germany
Posts: 2115
Status: 
Offline
 Hi Dom,

The new build is already a little bit overdue. We try to add as much fixes to it as possible. This delays it a bit but we hope to have the new build in the next days if no huge issue drops in.

Markus



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

 Posted: Mon Jul 12th, 2010 05:05 pm
PM Private Upload Quote Reply
dbush
Member
 

Joined: Tue Apr 1st, 2008
Location: London, United Kingdom
Posts: 12
Status: 
Offline
 Hi Markus,

Thanks for the update on when 307 will be available.

Regards,
Dom.
Back To Top PM Private Upload Quote Reply

 Posted: Mon Jul 12th, 2010 05:10 pm
PM Private Upload Quote Reply
dbush
Member
 

Joined: Tue Apr 1st, 2008
Location: London, United Kingdom
Posts: 12
Status: 
Offline
 Hi Jaakko,

Just seen your earlier message about me uploading the .sln rather than the .slp file, I'm afraid that I overlooked it earlier.

Many thanks for resolving this issue, despite me sending the wrong file.

Regards,
Dom.
Back To Top PM Private Upload Quote Reply

Current time is 08:46 pm  
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > VS2010 Silverlight 4 - errors during build



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