|
|||
|
|||
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius |
|
|||||||||||||
| Runtime Language Change - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
MagicFX Member
|
"Runtime Language Change" intrigues me. I just went throught the section about runtime language change of the help file and then I simply built the CSharp/Converter project by Microsoft Visual Studio 2005. However, Sisulizer DID NOT generate the "sisulizer.resources.dll" and "sisulizer.dll" at the root. What happened? Should I enable some options somewhere in Sisulizer? Another problem is that I can't open Net/Delphi project with CodeGear Delphi 2007. The Personality code seems to be imcompatible with Delphi 2007. Would you please fix these problems, thx!
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator 
|
1) .NET runtime language switch The code needed to perform language switch is in <sldir>NETSisulizer. Code is written in C# and Visual Studio 2005. The project file is Sisulizer.csproj Converter sample has two sources in Sisulizer project file: Converter.csproj (the application) and ....SisulizerSisulizer.csproj. When Sisulizer creates the output files (.resources.dll) it generates them to the default output directory of the VS project. This means that by default Converter.resources.dll files are written <sldir>NETCSharpConverterbinDebugxx where xx matches the languages. However Sisulizer.csproj's default output directory is <sldir>NETSisulizerbinDebug. Sisulizer creates them there. You can make Sisulizer to write the DLLs to the same directory as the main assembly. Right click the Sisulizer.csproj in the projct tree and choose Properies. Mofidy the output path. See the picture. You have to copy Sisulizer.dll assembly manually to the application directory. 2) Delphi 2007 and .NET Delphi 2007 is WIN32 only. It does not support .NET. Later this year CodeGear will release CodeGear Developer Studio 2007 that contains Delphi, C++Builder and .NET. However it is most likely that WinForms designed is not there any more but it supports only VCL.NET. Jaakko Attachment: untitled.PNG (Downloaded 49 times) Last edited on Fri Aug 24th, 2007 02:33 am by Jaakko.Salmenius ____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
MagicFX Member
|
thx Now i know where the problem is. I upgrade sisulizer from very very old version. it seems that the installshield did't upgrade the sample folders.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
MagicFX Member
|
Jaakko.Salmenius wrote: 2) Delphi 2007 and .NET http://www.codegear.com/products/radstudio/ CodeGear RAD is released recently. Does it support only VCL.NET? Last edited on Sat Sep 15th, 2007 11:28 am by MagicFX |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Jaakko.Salmenius Administrator
|
Yes
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| Current time is 01:05 am | |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Runtime Language Change | |
Sisulizer software localization tool - Three simple steps to localize
