|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > EInvalidCast when updating from Sisulizer Prof. 2008 to 2010
|
|
|||
|
.NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > EInvalidCast when updating from Sisulizer Prof. 2008 to 2010
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
||||||||||||||||
| EInvalidCast when updating from Sisulizer Prof. 2008 to 2010 - 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 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||
|
zuckermann_m Member
|
Hi, I just uprgraded from Sisulizer Professional 2008 Build 302 to 2010 Build 312 because we updated our .NET Solution to Visual Studio 2010. Opening my existing .slp file works, but when scanning the solution for changes I get the following error: 14:49:23 Fehler EInvalidCast: Ungültige Klassentypumwandlung. Call stack: 0040d4ab +40b Sisulizer.exe madStrings Replace 007b2720 +0dc Sisulizer.exe LaExcept TLaExcept.GetCallStack 00c45099 +0e1 Sisulizer.exe Log TLog.WriteException 00991496 +c0a Sisulizer.exe NetSource TNetProjectFolder.Scan 7c90e485 +009 ntdll.dll KiUserExceptionDispatcher 7c91045d +00c ntdll.dll RtlReleasePebLock 00966152 +212 Sisulizer.exe Win32Resource TWin32Resource.ScanResource 00966443 +10f Sisulizer.exe Win32Resource ScanPeResources 00966688 +138 Sisulizer.exe Win32Resource TWin32Resource.Scan 00991026 +79a Sisulizer.exe NetSource TNetProjectFolder.Scan 00996879 +0c9 Sisulizer.exe NetSource TNetProjectGroupSource.PerformScan 009968ca +002 Sisulizer.exe NetSource TNetProjectGroupSource.DoScan 00c9e727 +11b Sisulizer.exe Project TSource.Scan 00ca50fd +025 Sisulizer.exe Project ScanSource 00ca5263 +0d7 Sisulizer.exe Project ScanItem 00ca52ca +03a Sisulizer.exe Project I can send you the .slp file if you give me a secure way to transfer it. Can you give me a hint how to avoid this, or to localize the problem. Thanks in advance, Mathias Zuckermann Siemens AG
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator 
|
Hello Mathias, You could send to us this file via Private Upload feature. Files sent in this way are encrypted and password protected, so only our team members have access to them. Here is link to article about our upload system: http://www.the-localization-tool.com/?p=808 However, I fear we can't reproduce scan issue without your source files. Is this possible send to us this Visual Studio project files (solution and dependent files) via our upload system? If you are allowed send to us those files, please pack it as ZIP. Possible workarounds: 1. If this issue doesn't occur with Sisulizer 2008, try revert your Sisulizer to older build. Let me know, if you haven't installer of Sisulizer 2008. In this case I'll send link to our version archive. 2. Try create new project with Sisulizer 2010 for your Visual Studio project, and if this project works, try import translations from your old project. You could use advices from this http://www.the-localization-tool.com/?p=67 article (e.g. use"By context" or "By context first then by value" method and statuses import). Best regards,
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
|
|||||||||||||||||
|
zuckermann_m Member
|
Hello Janusz, Sisulizer 2008 Build 303 does the job. I just upgraded because I thought 2008 doesn't work with Visual Studio 2010 files. I cannot send you the source code, sorry. Is there another way to create logfiles or something similar? Nevertheless I will try to setup a new project with Sisulizer 2010. Best regards, Mathias
|
||||||||||||||||
| |||||||||||||||||
| |||||||||||||||||
|
Janusz Grzybek Super Moderator
|
Hello,I cannot send you the source code, sorry. Is there another way to create logfiles or something similar? OK, I understand. If you'll send your SLP file, I'll forward it to our R&D. Maybe they will find reason without access source files. You can see and export scan/build log via Sisulizer Output pane. Here is article how do it: http://www.the-localization-tool.com/?p=400 Please, attach zipped log file to uploaded SLP. Best regards, Janusz
____________________ http://www.sisulizer.com - Three simple steps to localize |
||||||||||||||||
| |||||||||||||||||
| Current time is 06:11 pm | |
| .NET, Delphi, ... - Sisulizer Localization Tool Support > Technical Support (You need to be registered at the forum to write) > Bugs and Quirks in Sisulizer > EInvalidCast when updating from Sisulizer Prof. 2008 to 2010 | |
Sisulizer software localization tool - Three simple steps to localize
