Trying to evaluate... but...crashes - Bugs and Quirks in Sisulizer - Technical Support (You need to be registered at the forum to write) - .NET, Delphi, ... - Sisulizer Localization Tool Support

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.

Not logged in - Login | Register

.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > Trying to evaluate... but...crashes

Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius

Page: 1 2

Printer Friendly

Trying to evaluate... but...crashes - 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

Posted: Wed Jan 27th, 2010 08:32 am

rvacaru
Member

Joined:	Wed Jan 27th, 2010
Location:
Posts:	43
Status:	Offline

Hi

I am trying to evaluate the Sisulizer Enterprise edition....

I get this in the log

10:28:01 AM Error Exception: Not a resource dictionary. Call stack:  00769f93 +40b Sisulizer.exe madStrings         Replace  007b14a4 +0dc Sisulizer.exe LaExcept           TLaExcept.GetCallStack  00c33d85 +0e1 Sisulizer.exe Log                TLog.WriteException  00bcf09a +3e6 Sisulizer.exe NetAssemblyScanner TNetAssemblyScanner.ProcessResource  7c91045d +00c ntdll.dll                        RtlReleasePebLock  007da5d3 +227 Sisulizer.exe NetMetadata        TNetMetadata.GetResources  004c3633 +037 Sisulizer.exe Themes             TThemeServices.DrawElement  00b82eb6 +03e Sisulizer.exe MainFrm            DrawFilter  7c90e470 +010 ntdll.dll                        KiUserCallbackDispatcher  004b9a9f +03b Sisulizer.exe Controls           TWinControl.WMPaint  004846c1 +015 Sisulizer.exe ComCtrls           TCustomStatusBar.WMPaint  004b4c7e +2d2 Sisulizer.exe Controls           TControl.WndProc  004b9183 +513 Sisulizer.exe Controls           TWinControl.WndProc  004b889c +02c Sisulizer.exe Controls           TWinControl.MainWndProc  0043c1f4 +014 S
10:28:02 AM Error Exception: Node "designer.Menu[0]" already exists. Call stack:  00769f93 +40b Sisulizer.exe madStrings      Replace  007b14a4 +0dc Sisulizer.exe LaExcept        TLaExcept.GetCallStack  00c33d85 +0e1 Sisulizer.exe Log             TLog.WriteException  00c918c6 +086 Sisulizer.exe Project         ScanItems  7c90e485 +009 ntdll.dll                     KiUserExceptionDispatcher  00985b2c +020 Sisulizer.exe XamlNode        TXamlMenuNode.SetMenu  00985f6a +052 Sisulizer.exe XamlNode        AddMenus  00985f8d +075 Sisulizer.exe XamlNode        AddMenus  00985fb9 +01d Sisulizer.exe XamlNode        TXamlFormNode.CheckMenus  00985fe8 +00c Sisulizer.exe XamlNode        TXamlFormNode.AfterScan  00c85668 +028 Sisulizer.exe Project         TNode.AfterScan  0096b590 +00c Sisulizer.exe NetFormNode     TNetFormFolder.AfterScan  00c85668 +028 Sisulizer.exe Project         TNode.AfterScan  00c8ad61 +005 Sisulizer.exe Project         TSource.AfterScan  00c2424c +008 Sisulizer.exe ComponentSource TComponentSource.AfterScan  00c1961d +021 Sisulizer.exe BaseSo
10:28:02 AM

The application is quite big and we use the Actipro software components.

Any advice?

Posted: Wed Jan 27th, 2010 12:13 pm

Markus.Kreisel
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Bedburg, Germany
Posts:	1815
Status:	Offline

Hi,

Please zip the following files:

- assembly file (exe or dll) and all custom assemblies it uses
- Sisulizer project file (slp)

Then upload the files to us and we take a look. Please use the "Private Upload" button right above this post. It helps us to keep track of uploads and forums posts.

With a little bit luck we can solve that problem quickly and include a fix in the next build.

Markus

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Wed Jan 27th, 2010 02:18 pm

rvacaru
Member

Joined:	Wed Jan 27th, 2010
Location:
Posts:	43
Status:	Offline

You got a PM from me with the link to our application.
Thank you in advance

Regards
Radu

Posted: Wed Jan 27th, 2010 02:28 pm

Markus.Kreisel
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Bedburg, Germany
Posts:	1815
Status:	Offline

Thanks, we'll take a look

Markus

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Fri Jan 29th, 2010 07:54 am

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Espoo, Finland
Posts:	2275
Status:	Offline

Thank you for the files. I managed to fix that bug but there is another. In order to fix it I would need views\scenariowindowpage.xaml file. Can you upload it to me?

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Sat Jan 30th, 2010 08:20 am

rvacaru
Member

Joined:	Wed Jan 27th, 2010
Location:
Posts:	43
Status:	Offline

Done.

Posted: Sat Jan 30th, 2010 12:32 pm

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Espoo, Finland
Posts:	2275
Status:	Offline

Thank you for the file. The problem Sisulizer had was this:

In XAML you give a name/id to a control by using x:Uid, x:Name or Name attribute. We assumed that the name is always unique. This is tru in the case you use either x:Name or Name attributes but .NET lets you enter two or more same names in x:Uid attributes. Your XAML contained such duplicates ids. I fixed this in build 297. Now Sisulizer accepts duplicate x:Uid values.

New build will come out next week.

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Sat Jan 30th, 2010 12:43 pm

rvacaru
Member

Joined:	Wed Jan 27th, 2010
Location:
Posts:	43
Status:	Offline

Thank you!

I'm looking forward to testing it.

PS: We didn't really pay attention to the x:Uid generation as we started just few days ago to investigate how to localise our app

Last edited on Sat Jan 30th, 2010 12:48 pm by rvacaru

Posted: Sun Jan 31st, 2010 08:31 am

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Espoo, Finland
Posts:	2275
Status:	Offline

Sisulizer (build 297) can now correctly scan your assembly. I will still test creating of localized satellite assebly files. In order to do that I need to have the custom DLLs that the EXE uses. Can you send them to me.

AMADEE.Wpf.DataAgent.dll
AMADEE.Wpf.Designer.Views.dll
AMADEE.Wpf.Designer.Views.UserControls.dll
...

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Sun Jan 31st, 2010 02:18 pm

Janusz Grzybek
Super Moderator

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

We were having link to installer of your application and I forwarded it to Jaakko. We let you know if we will need additional files.

Best,
Janusz

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Sun Jan 31st, 2010 03:30 pm

rvacaru
Member

Joined:	Wed Jan 27th, 2010
Location:
Posts:	43
Status:	Offline

In the meanwhile I uploaded the dlls via Private Upload so he has 2 sources now

Posted: Mon Feb 1st, 2010 07:41 am

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Espoo, Finland
Posts:	2275
Status:	Offline

Can you send me ContentProviderDictionary.xaml?

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Mon Feb 1st, 2010 08:23 am

rvacaru
Member

Joined:	Wed Jan 27th, 2010
Location:
Posts:	43
Status:	Offline

Done.

Posted: Sat Feb 6th, 2010 11:04 am

Jaakko.Salmenius
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Espoo, Finland
Posts:	2275
Status:	Offline

Can you send me Dictionaries\DataAgentDictionaries\CommonDictionary.xaml?

Jaakko

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Tue Feb 9th, 2010 01:13 pm

rvacaru
Member

Joined:	Wed Jan 27th, 2010
Location:
Posts:	43
Status:	Offline

When do you estimate the Build 297 will be released?

Posted: Tue Feb 9th, 2010 01:15 pm

Renate.Reinartz
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Bedburg, Germany
Posts:	52
Status:	Offline

Hi,

I write you some PM.

____________________
http://www.sisulizer.de - Three simple steps to localize

Posted: Wed Feb 10th, 2010 08:27 am

rvacaru
Member

Joined:	Wed Jan 27th, 2010
Location:
Posts:	43
Status:	Offline

Cool, the current build looks much better

One question though... why I cannot see the strings inside CommandDictionary.xaml (AMADEE.Wpf.Designer.Commands.dll)?
There are some Label="" there that I would also like to translate...

Posted: Wed Feb 10th, 2010 09:30 am

rvacaru
Member

Joined:	Wed Jan 27th, 2010
Location:
Posts:	43
Status:	Offline

Try to localize AMADEE.Wpf.Help. Error below. I fixed it by adding unique UIds to all PopupButton.Menu items.

"11:26:03 AM Scanning file "C:Documents and Settingsradu.dan.vacaruMy DocumentsVisual Studio 2008ProjectsAMADEEDesignerbinDebugAMADEE.Wpf.Help.dll"
11:26:03 AM Hint helpviewercontrol.CommandBinding[0] component has no name. It is recommended to give a name using either Name, x:Name or x:Uid attribute.
11:26:03 AM Hint helpviewercontrol.CommandBinding[1] component has no name. It is recommended to give a name using either Name, x:Name or x:Uid attribute.
11:26:03 AM Hint helpviewercontrol.CommandBinding[2] component has no name. It is recommended to give a name using either Name, x:Name or x:Uid attribute.
11:26:03 AM Hint helpviewercontrol.CommandBinding[3] component has no name. It is recommended to give a name using either Name, x:Name or x:Uid attribute.
11:26:03 AM Hint helpviewercontrol.CommandBinding[5] component has no name. It is recommended to give a name using either Name, x:Name or x:Uid attribute.
11:26:03 AM Hint helpviewercontrol.CommandBinding[6] component has no name. It is recommended to give a name using either Name, x:Name or x:Uid attribute.
11:26:03 AM Hint helpviewercontrol.CommandBinding[7] component has no name. It is recommended to give a name using either Name, x:Name or x:Uid attribute.
11:26:03 AM Hint helpviewercontrol.CommandBinding[8] component has no name. It is recommended to give a name using either Name, x:Name or x:Uid attribute.
11:26:03 AM Hint helpviewercontrol.CommandBinding[9] component has no name. It is recommended to give a name using either Name, x:Name or x:Uid attribute.
11:26:03 AM Hint helpviewercontrol.CommandBinding[10] component has no name. It is recommended to give a name using either Name, x:Name or x:Uid attribute.
11:26:03 AM Hint Picture data type is currently excluded. Use source dialog to include the data type.
11:26:03 AM Error Exception: Node "helpviewercontrol.PopupButton[0].Menu[0]" already exists. Call stack: 0040d44f +40b Sisulizer.exe madStrings Replace 007b0248 +0dc Sisulizer.exe LaExcept TLaExcept.GetCallStack 00c39389 +0e1 Sisulizer.exe Log TLog.WriteException 00c98a4a +096 Sisulizer.exe Project ScanItems 7c90e485 +009 ntdll.dll KiUserExceptionDispatcher 00986b0d +091 Sisulizer.exe XamlNode AddMenus 00986b49 +0cd Sisulizer.exe XamlNode AddMenus 00986baa +022 Sisulizer.exe XamlNode TXamlFormNode.CheckFormMenus 00986bbe +00a Sisulizer.exe XamlNode TXamlFormNode.CheckMenus 00986be8 +00c Sisulizer.exe XamlNode TXamlFormNode.AfterScan 00c8c7d4 +028 Sisulizer.exe Project TNode.AfterScan 0096c050 +00c Sisulizer.exe NetFormNode TNetFormFolder.AfterScan 00c8c7d4 +028 Sisulizer.exe Project TNode.AfterScan 00c91ecd +005 Sisulizer.exe Project TSource.AfterScan 00c29664 +008 Sisulizer.exe ComponentSource TComponentSource.AfterScan 00c1e6a1 +021 Sisulizer.exe
11:26:03 AM
11:26:03 AM There are new items in the project
11:26:03 AM 21 new node(s)
11:26:03 AM 91 new component(s)
11:26:03 AM 67 new row(s)
11:26:03 AM 23 new string row(s)
11:26:03 AM
11:26:03 AM

= New row status. The row has been added to the project in the previous scan(s)
11:26:03 AM To clear new statuses choose Project | Clear New Status
11:26:03 AM
11:26:03 AM Errors: 1
11:26:03 AM Elapsed time 687 ms
"

Last edited on Wed Feb 10th, 2010 09:38 am by rvacaru

Posted: Thu Feb 11th, 2010 09:08 am

Markus.Kreisel
Administrator

Joined:	Sat Apr 8th, 2006
Location:	Bedburg, Germany
Posts:	1815
Status:	Offline

Hi,

Just to make sure about that

Label =

thing. Is that in your source code? Is it perhaps a hard-coded string? These need to be resourced first. The stuff in dialogs is resourced automatically. But for strings in source code this is a manual step you have to do once.

Markus

____________________
http://www.sisulizer.com - Three simple steps to localize

Posted: Fri Feb 12th, 2010 08:00 am

rvacaru
Member

Joined:	Wed Jan 27th, 2010
Location:
Posts:	43
Status:	Offline

There is a misunderstanding here...

I have a ResourceDictionary that has strings inside. They should be parsed/localized by Sisulizer too...

Current time is 06:41 pm	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 > Trying to evaluate... but...crashes

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