|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > build 295 crashes when scanning for changes
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > build 295 crashes when scanning for changes
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | ||
| Author | Post | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
bikedude Member
|
My application uses a number of WPF components. In one particular form, there is a grid that clearly is not loaded correctly. If I delete the translated resource files, it looks OK. In build 291, SL crashes during the project scan. (we submitted the bug report which looked like it had been generated by madExcept btw, very nice) We upgraded from build 291 to 295 to see if that could help, and now, when we scan for changes we simply get an "Invalid pointer operation" or an "Invalid class typecast" when we try saving the project. This time, no automatic error report submission form was available. |
|||||||||
|
Janusz Grzybek Super Moderator 
|
Hello, Thank you for information. This is known issue. It was fixed in build 296 and with this build madExpect should work correctly. Next build will come out in next days. Janusz, |
|||||||||
|
bikedude Member
|
...but meanwhile I have problems with Sisulizer not accepting my XAML code. Have you made any changes to the WPF support too, in build 296? |
|||||||||
|
Janusz Grzybek Super Moderator
|
Could you send to us via our upload form your source .NET file(s) for your Sisulizer's project? We'll check it. Janusz |
|||||||||
|
bikedude Member
|
I think the problem could be related to a grid that used to be a WPFToolkit DataGrid, but we recently changed it to a different grid that inherits from the DataGrid. Maybe we haven't properly added the new grid to the Sisulizer project? (Do we need to?) |
|||||||||
|
bikedude Member
|
.zip with project provided as a private upload. |
|||||||||
|
Janusz Grzybek Super Moderator
|
Hello, Thank you for files. I reproduced issue. Have a nice weekend, Janusz |
|||||||||
|
Jaakko.Salmenius Administrator 
|
When Sisulizer compile XAML file it needs to find all assembly files that XAML refers directly or indirectly. I have Mikromarc.Windows.WPFComponents.dll but it seems to use Mikromarc.Common.Remoting.dll. Can you send it to me and any other custom DLLs that Mikromarc.Windows.WPFComponents.dll uses. Jaakko |
|||||||||
|
bikedude Member
|
Hmm, something happened with the version I attached. Could you try to replace the wpfdatagrid.cs file with the one in the next private upload please? |
|||||||||
|
Jaakko.Salmenius Administrator
|
Sisulizer correctly creates localized XAML file but it fails to compile some of them. Compilation is need to create localized satellite assembly files. In order to compile XAML file Sisulizer needs to have all assembly files used by the XAML file. Your project uses several 3rd party assembly files that I don't have. Also the output directory of your project is ..\..\..\Bin and it was out of the scope of the zip file your send. Can you send a new project zip file that contains ..\..\..\Bin the assembly files (they are most likely in ..\..\..\Bin). Jaakko Attachment: Untitled.png (Downloaded 6 times) |
|||||||||
|
Jaakko.Salmenius Administrator
|
No need to send anything. I found your assembly xxxx.Windows.WPFComponents.dll in objDebug directory. Also I downloaded WPFToolkit. That was only 3rd party component your XAML files really used. Now I managed to compile the XAML file and create localized satellite assembly files. Your Sisulizer version can not compile because it did not create compile assembly file list to pass the XAML compiler. I fixed this in build 297. The new build also fixes the bug your reported in your first message. The new build will come out in few days. Jaakko |
|||||||||
Sisulizer software localization tool - Three simple steps to localize