|
|||
|
.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 .NET WPF project (attached errors)
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page: 1 2 |
|
|||||||||||||||
| Can't build .NET WPF project (attached errors) - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support | |||||||||||||||||
| Author | Post | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
rvacaru Member
|
We unsuccessfully tried to localize a smaller project... I attached the zip files with the errors. One seems to be related to lowercasing "run" and the other one is complaining that an internal class is "not public or internal"
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rvacaru Member
|
I attach another zip file with same error I reported already. During translation some tokens get lowercased. I had a <Hyperlink Command="blabla"/> and after translation in the finishpage.de.xaml it appears <hyperlink command="blabla"/> and of course building the project fails....
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thank you for the files you sent. Sisulizer could not compile the localized XAML file. The problem was that Sisulizer uses incorrect path. It figure our why this happened I would like to know: Did you use binary localization or project localization? In binary localization you added assembly files (.exe or .dll) into Sisulizer project. In project localization you added .csproj or .sln. Can you send you Sisulizer project file (.slp). If you use binary localization can you also send the assembly file ( ????.Licensing.Management.dll) and the assemblies (.dll) that it uses. If you use project localization can you send the ????.Licensing.Management.csproj file. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rvacaru Member
|
We are using project localization (.csproj). I'll upload both .slp and .csproj in the next 2 hours as soon as I reach my desk at office. Thank you for support
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
rvacaru Member
|
Requested files were uploaded.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thank you for the files. Can you also send WizardPages\Finish.xaml Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
rvacaru Member
|
Done
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Jaakko.Salmenius Administrator
|
Thank you for the file. I found the bug and start fixing it. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
rvacaru Member
|
Is this fixed in 303? EDIT: Seems the casing is almost fixed. But there is still a problem there; see below: <Hyperlink command="management:LicensingDialog.ReregisterCommand" should obviously be <Hyperlink Command="management:LicensingDialog.ReregisterCommand" (the casing for the Command is wrong). EDIT2: The second problem I couldn't find out why it happens; here's the error message: Build FAILED. "C:\Users\jonathan.chapman\Documents\Visual Studio 2010\Projects\AMADEE\Licensing.Management\LicensingDialog.proj" (ResolveReferences;MarkupCompilePass1;MarkupCompilePass2 target) (1) -> (MarkupCompilePass1 target) -> C:\Users\jonathan.chapman\Documents\Visual Studio 2010\Projects\AMADEE\Licensing.Management\LicensingDialog.de.xaml(53,48): error MC3050: Cannot find the type 'BpmConnectionSettings'. Note that type names are case sensitive. [C:\Users\jonathan.chapman\Documents\Visual Studio 2010\Projects\AMADEE\Licensing.Management\LicensingDialog.proj] Last edited on Thu Apr 29th, 2010 09:11 am by rvacaru |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rvacaru Member
|
Bump
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, We did not forget you. We just had been pretty busy the last days. Your issue is on the to-do list of our R&D. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rvacaru Member
|
Trying the Bing Translator I noticed the lowercasing problem is caused by Microsoft Translator. They are lowercasing nodenames for XML structures sent for translation Sorry for reporting it but it seems not to be a Sisulizer bug. I'll give today another try to localize our app (with 306). I hope I'll be successful this time PS: Maybe we should "push" Microsoft to improve the XML support for translations
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, Thanks for the feedback. Google and Microsoft Translate improve all the time. 306 uses a newer API for MS Translate. Perhaps that does the trick. It is recommended to use an own API key for both services. If all Sisulizer users use the same key too often the services block the key. Better use an own. There is an article planned on our blog how to get the API keys. So stay tuned. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rvacaru Member
|
Oh, thanks for the API key suggestion. Actually we have one but I omitted to put it to Sisulizer.
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
rvacaru Member
|
Now I got .NET SDK installed... I am trying to localize the csproj... I am getting errors in 61 files (61 .zip files). I can't upload all (100MB) but I will upload some of them. Comparing the original.xaml with original.de.xaml everything seems perfect. BUT... for example: "error MC3028: Cannot add content to object of type 'AMADEE.Wpf.DataAgent.DataAgentDataProvider'. Line 21 Position 14. [C:\Documents and Settings\radu.dan.vacaru\My Documents\Visual Studio 2010\Projects\AMADEE\Designer\RSSReader.proj]" Why is this happening? Invalid referenced assembly? Thanks in advance for any help
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
rvacaru Member
|
Another WPF related error: <TextBlock Grid.Row="0"> <Run>Thank you for using</Run> <Run Text="{x:Static license:ApplicationLicense.ProductName}"/> <Run>.</Run> <LineBreak/> </TextBlock> Gets translated as: <TextBlock Grid.Row="0"><Run>Vielen Dank für die Verwendung von</Run> <Run>{x:Static license:ApplicationLicense.ProductName}</Run> <Run>.</Run></TextBlock> It seems the Text="" attribute was removed...
|
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
rvacaru Member
|
Another attempt to localize our project...another failure Attached error log and all zip files.
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hi, I saw in your last upload that you are using binary localization. Is that correct? I spoke with our R&D and they recommend to use project localization for WPF instead. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
rvacaru Member
|
I am using project localization (the only file I have in my slp project is the .csproj).
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Markus.Kreisel Administrator
|
Hmm, In the files you send there is no .slp and no .csproj. I guess you mean .proj? Or did you send the wrong files? In your error_log.txt Sisulizer are a lot rows like Please send "C:\Documents and Settings\radu.dan.vacaru\My Documents\Visual Studio 2010\Projects\AMADEE\Designer\Controls\RSSReader.de.zip" file to Sisulizer support team. This log does not match the files you send. I also do not have these files requested. In the moment I don't know how to reproduce your problem. Could you please do the following: Please create a simple sample. As simple as can be. It seems that all the errors in your log have one, perhaps two reasons. It would be absolutely enough to have a project showing the problem only once. I need all files to reproduce the issue plus a detailed description how to reproduce. If your sample creates an error log it might create .zip files with needed files for a fix. Please also include these. Make it as short and easy as possible. Sorry, in the moment this thread is mixing solved and unsolved issues and we need a clear restart focusing on one issue at one time. Everything else will be confusing and we will not talk about the same issues. Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:01 am | Page: 1 2 |
| .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 .NET WPF project (attached errors) | |
Sisulizer software localization tool - Three simple steps to localize