|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Build order with WPF controls
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Build order with WPF controls
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| Build order with WPF controls - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
robson Member
|
Hello I 'm using Sisulizer with WPF controls, where one control (ControlOne) relies on another control (ControlTwo from another DLL). The problem I have is that ControlOne assembly is created before ControlTwo in Sisulizer, and therefore it is not recognized, and the build fails. How can I set the build order of the assemblies in Sisulizer? Thanks and regards Robert
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Could you tell me more about your sources for Sisulizer project? I think it would be helpful if you upload to us your output message from build operation via "Private Upload" button on toolbar of forum post. More about output messages you can find in this article on our blog: http://www.the-localization-tool.com/?p=400. This information can tell us something about your project, source files and if we need also other your files (source files, Sisulizer project file). Of course, all files sent to us via our upload form are password protected and only Sisulizer team members have access to these files. If controls mentioned in your post belong to different sources (first level nodes in Project Tree) in your Sisulizer project, you can use following trick – first, right click on source node with ControlTwo control and select "Build in All languages", next right click on source node with ControlOne control and use this same feature via context menu of source item in Project tree. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
robson Member
|
Hello The message is: Could not compile "ReportUserControl.fi.xaml" file. Microsoft (R) Build Engine Version 3.5.30729.1 [Microsoft .NET Framework, Version 2.0.50727.3603] Copyright (C) Microsoft Corporation 2007. All rights reserved. Build started 3/15/2010 2:29:05 PM. Project "C:GivenCodeProjectsSourcesRapidCommonGUIGiven.Rapid.UIReportUserControl.proj" on node 0 (ResolveReferences;MarkupCompilePass1;MarkupCompilePass2 target(s)). C:GivenCodeProjectsSourcesRapidCommonGUIGiven.Rapid.UIDialogsReportUserControl.fi.xaml(15,18): error MC3074: The tag 'DataGrid' does not exist in XML namespace '[url=http://schemas.microsoft.com/wpf/2008/toolkit'.]http://schemas.microsoft.com/wpf/2008/toolkit'.[/url] Line 15 Position 18. Done Building Project "C:GivenCodeProjectsSourcesRapidCommonGUIGiven.Rapid.UIReportUserControl.proj" (ResolveReferences;MarkupCompilePass1;MarkupCompilePass2 target(s)) -- FAILED. Build FAILED. "C:GivenCodeProjectsSourcesRapidCommonGUIGiven.Rapid.UIReportUserControl.proj" (ResolveReferences;MarkupCompilePass1;MarkupCompilePass2 target) (1) -> (MarkupCompilePass1 target) -> C:GivenCodeProjectsSourcesRapidCommonGUIGiven.Rapid.UIDialogsReportUserControl.fi.xaml(15,18): error MC3074: The tag 'DataGrid' does not exist in XML namespace '[url=http://schemas.microsoft.com/wpf/2008/toolkit'.]http://schemas.microsoft.com/wpf/2008/toolkit'.[/url] Line 15 Position 18. 0 Warning(s) 1 Error(s) Time Elapsed 00:00:00.71 I provided via Provate Upload, a test project with very simply xaml control using an external resource (DataGrid), and Sisulzier fails to compile it... Last edited on Mon Mar 15th, 2010 03:44 pm by robson |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Thank you for your example. I'll reproduced error with this sample project. We'll ltet you know about our investigation result. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
Jaakko.Salmenius Administrator 
|
Thank you for the sample. Sisulizer failed to include WPFToolkit into the compiel project when compiling XAML file that refers to http://schemas.microsoft.com/wpf/2008/toolkit I fixed this in build 301. The new build will come out in next week. Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
robson Member
|
Thanks for the update, looking forward to test it :-)
|
||||||||||||||||
| |||||||||||||||||
| Current time is 09:00 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Build order with WPF controls | |
Sisulizer software localization tool - Three simple steps to localize
