2. .NET Add-In - Recent Threads

How to enable Setup button

Balázs Fehér — Wed, 18 Jun 2025 06:44:55 GMT

Hi All,

As part of my ongoing work with SDL Passolo, I've developed a custom add-in that includes several features. In the interface of Passolo add-in manager, there's a visible "Setup" button – as shown in the image below – which ideally should allow users to open a configuration dialog where they can manage custom plugin settings.

However, while exploring the Passolo SDK documentation, I couldn’t find any direct reference or example that explains how to link this Setup button to a custom settings window or handler within the plugin code. Is it possible to bind to any "kind" of plugin? If yes, may i ask how? (Or is this button only available for some special types, like "Export/import addins?)

Thanks in advance for your reply.

Generating .NET Satellite assemblies: errors only once in a Passolo session

Franz-Josef Knelangen — Wed, 11 Jun 2025 08:47:43 GMT

When generating *.resources.dll files in a project for the first time after opening Passolo and the LPU, several error messages appear—eight in total, with some repeating (see screenshots below).

Although the UI language is set to English, the error messages are in German or a mix of languages. I couldn’t find any information about these errors in the Passolo documentation.

After dismissing the errors and generating the target files again, the errors no longer appear.

I suspect these initial errors are making my automated builds using batch files unreliable, as the builds periodically fail without any errors being logged.

Any idea how to check or fix this?

Best regards,
Franz-Josef

Reinstalling Add-Ins when moving Passolo to a new machine

Mark Pfeifer — Tue, 03 Jun 2025 16:53:52 GMT

We've been using Passolo since Passolo 2015. We bought Passolo 2015 along with the .Net and Delphi add-ins. We upgraded twice and currently run Passolo 2022.

I need to move this installation to a new machine. I installed Passolo 2022 and transferred the license - this all works well. The problem is the add-ins. How do I get these add-ins to work on the new machine? Do I need to purchase Passolo 2022 versions of the add-ins?

Can I make an add-in originally purchased for Passolo 2015 work on Passolo 2022?

Addin version does not appear

Balázs Fehér — Thu, 29 May 2025 05:23:14 GMT

Hi All,

I have a problem that, I have a functioning addin, but the version of the addin does not appear in the options (see image). I am not sure what I am doing wrong. Can you please help what I should set to make it appear?

PSL exception parsing source files - after project update containing modularization with NuGet packages

Franz-Josef Knelangen — Mon, 12 May 2025 07:57:40 GMT

Project contains .NET 4.8 and .NET 8 DLLs - running on different cad platforms. No problem so far.

Project was updated - same .NET 4.8 and .NET 8 mix - and makes now use of NuGet packages.

Result: Parser exception with every DLL in there - .NET 4.8 or .NET 8 makes no difference.

Debugger always stops at "ToLower (string str)" function. Stack see below.

dotPeek or JustDecompile show the content w/o problems, only diff. ist the 1.0.56.4 vs. 1.0.78.0 - see screenshot.

I don't have any clue how this can be resolved...

Greetings,

Franz-Josef

Stack:

> mscorlib.dll!System.Globalization.TextInfo.ToLower(string str) Zeile 387 C#
mscorlib.dll!string.ToLower(System.Globalization.CultureInfo culture) Zeile 3157 C#
ReflectionHelper.dll!ReflectionHelper.Assembly.AssemblyDefinitionManager.GetAssemblyFromCache(string fullAssemblyName) Unbekannt
ReflectionHelper.dll!ReflectionHelper.Assembly.AssemblyDefinitionManager.FindAssembly(string fullAssemblyName) Unbekannt
ReflectionHelper.dll!ReflectionHelper.Assembly.AssemblyResolverHelper.Resolve(Mono.Cecil.AssemblyNameReference name) Unbekannt
Mono.Cecil.dll!Mono.Cecil.MetadataResolver.Resolve(Mono.Cecil.TypeReference type) Unbekannt
Mono.Cecil.dll!Mono.Cecil.MetadataResolver.GetType(Mono.Cecil.ModuleDefinition module, Mono.Cecil.TypeReference reference) Unbekannt
Mono.Cecil.dll!Mono.Cecil.MetadataResolver.Resolve(Mono.Cecil.TypeReference type) Unbekannt
[Die 2 Frames darüber wurden 17849-mal wiederholt]
Mono.Cecil.dll!Mono.Cecil.MetadataResolver.GetType(Mono.Cecil.ModuleDefinition module, Mono.Cecil.TypeReference reference) Unbekannt
Mono.Cecil.dll!Mono.Cecil.MetadataResolver.Resolve(Mono.Cecil.TypeReference type) Unbekannt
Mono.Cecil.dll!Mono.Cecil.TypeReference.Resolve() Unbekannt
Mono.Cecil.dll!Mono.Cecil.Mixin.CheckedResolve(Mono.Cecil.TypeReference self) Unbekannt
Mono.Cecil.dll!Mono.Cecil.SignatureReader.ReadCustomAttributeEnum(Mono.Cecil.TypeReference enum_type) Unbekannt
Mono.Cecil.dll!Mono.Cecil.SignatureReader.ReadCustomAttributeElementValue(Mono.Cecil.TypeReference type) Unbekannt
Mono.Cecil.dll!Mono.Cecil.SignatureReader.ReadCustomAttributeElement(Mono.Cecil.TypeReference type) Unbekannt
Mono.Cecil.dll!Mono.Cecil.SignatureReader.ReadCustomAttributeElement(Mono.Cecil.TypeReference type) Unbekannt
Mono.Cecil.dll!Mono.Cecil.SignatureReader.ReadCustomAttributeFixedArgument(Mono.Cecil.TypeReference type) Unbekannt
Mono.Cecil.dll!Mono.Cecil.SignatureReader.ReadCustomAttributeConstructorArguments(Mono.Cecil.CustomAttribute attribute, Mono.Collections.Generic.Collection<Mono.Cecil.ParameterDefinition> parameters) Unbekannt
Mono.Cecil.dll!Mono.Cecil.MetadataReader.ReadCustomAttributeSignature(Mono.Cecil.CustomAttribute attribute) Unbekannt
Mono.Cecil.dll!Mono.Cecil.CustomAttribute.Resolve.AnonymousMethod__35_0(Mono.Cecil.CustomAttribute attribute, Mono.Cecil.MetadataReader reader) Unbekannt
Mono.Cecil.dll!Mono.Cecil.ModuleDefinition.Read<System.__Canon>(System.__Canon item, System.Action<System.__Canon, Mono.Cecil.MetadataReader> read) Unbekannt
Mono.Cecil.dll!Mono.Cecil.CustomAttribute.Resolve() Unbekannt
Mono.Cecil.dll!Mono.Cecil.CustomAttribute.ConstructorArguments.get() Unbekannt
ReflectionHelper.dll!ReflectionHelper.DotNetHelper.IsLocalizableProperty(Mono.Cecil.TypeDefinition td, string propertyname) Unbekannt
ReflectionHelper.dll!ReflectionHelper.DotNetHelper.IsLocalizableProperty(Mono.Cecil.TypeReference tr, string propertyName) Unbekannt
WFControlModel.dll!DnDotNet.WFControlModel.WFControl.AddDefaultValues(string typename, DnDotNet.WFControlModel.WFPropertyList values, bool isformcontrol, bool addFont, bool isinheritedfromform) Unbekannt
WFControlModel.dll!DnDotNet.WFControlModel.WFControl.AddDefaultValues(string typename, DnDotNet.WFControlModel.WFPropertyList values, bool isformcontrol, bool addFont, bool isinheritedfromform) Unbekannt
WFControlModel.dll!DnDotNet.WFControlModel.WFControl.AddDefaultValues(bool isAutoScaleModeEqualsFontFound) Unbekannt
DnDotNet.dll!DnDotNet.Parser.Resources.WFFormResource.AddDefaultValues() Unbekannt
DnDotNet.dll!DnDotNet.Parser.Resources.AssemblyResource.ParseAndExtend(ref DnDotNet.Parser.Resources.WFFormResource form, DnDotNet.Parser.Resources.WFFormResource baseForm) Unbekannt
DnDotNet.dll!DnDotNet.Parser.Resources.AssemblyResource.ParseAssemblyDefinition(Mono.Cecil.AssemblyDefinition currentAssemblyDefinition, System.Collections.Generic.Dictionary<string, DnDotNet.Parser.Resources.IResource> missingResources, bool handleSatelliteAsMain) Unbekannt
DnDotNet.dll!DnDotNet.Parser.Resources.AssemblyResource.Parse() Unbekannt
DnDotNet.dll!DnDotNet.Parser.WFParser.AppDomainRunner.Parse(string fileName, Pass.AddIn.Core.enmParsingTypes action, Pass.AddIn.Core.CPAICustomFile customFile, Pass.AddIn.Core.CPAIAddIn addin, Pass.AddIn.Core.CPAIApplicationTools apptools) Unbekannt
DnDotNet.dll!DnDotNet.Parser.WFParser.AppDomainRunner.Invoke() Unbekannt
DnDotNet.dll!DnDotNet.Parser.WFParser.AppDomainRunnerMarshal.Invoke() Unbekannt
[AppDomain (Sandbox, #2) -> AppDomain (DefaultDomain, #1)]
mscorlib.dll!System.AppDomain.DoCallBack(System.CrossAppDomainDelegate callBackDelegate) Unbekannt
[AppDomain (DefaultDomain, #1) -> AppDomain (Sandbox, #2)]
DnDotNet.dll!DnDotNet.Parser.WFParser.ParserAppDomain.ParseUsingAppDomain(string filename, Pass.AddIn.Core.enmParsingTypes action, Pass.AddIn.Core.CPAICustomFile customFile, Pass.AddIn.Core.CPAIAddIn addin, Pass.AddIn.Core.CPAIApplicationTools apptools, bool cacheassemblies) Unbekannt
DnDotNet.dll!DnDotNet.Parser.WFParser.ParserAppDomain.ParseDotNetFile(string filename, Pass.AddIn.Core.enmParsingTypes action, Pass.AddIn.Core.CPAICustomFile customFile) Unbekannt
DnDotNet.dll!DnDotNet.Components.ParserComponent.ParseFile(string fileName, Pass.AddIn.Core.enmParsingTypes action, Pass.AddIn.Core.CPAICustomFile customFile) Unbekannt
PAINetAddInManager.dll!<Module>.PAIFN_ParseFile(char* filename, int action, IPAICustomFile* customfile) Unbekannt

Passolo 2022 Professional -- what does this error mean ?

Robert Yang — Fri, 20 Dec 2024 16:23:41 GMT

Hi, we've been using Passolo 2022 for two years now, and things seem to be working pretty well. Lately though we ran into an error when we tried to add a new DLL to our LPU.

We are on .Net Framework 4.8, with a mix of Windows Forms and WPF. None of this has caused any issues so far. But this one DLL which contains WPF XAML and a couple of XML files as string resources seems to cause issues with the .Net parser when trying to create/update the string table for the first time.

Here is an excerpt of the error, omitting the specific filename and so on :

    Passolo: Professional Edition 2022
    DotNet Parser Version: 22.0.207.0

Info
        ObfuscationLevel: None
        Winform ResourceReader Schemes: None
        Assembly
            Target Framework: Framework 4.0
            PortableExecutableKinds: ILOnly
            ImageFileMachine: I386
            Assembly is Unsigned
    
    Referenced Assemblies
        mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 
        PresentationCore, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 
        PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 
        System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 
        System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 
        System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 
        System.Data.DataSetExtensions, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 
        System.Drawing, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a 
        System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 
        System.Xml, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089 
    
    Missing Fonts
        None

Exception: The type initializer for 'Pass.Silverlight.SilverlightAssemblyResolver' threw an exception.
    InnerException Exception: Could not find Silverlight.
       at Pass.Silverlight.SilverlightAssemblyResolver..ctor(String targetAssembly)
   at Pass.Silverlight.SilverlightAddIn.ParseFile(String file, Int32 action, CPAICustomFile customFile, CPAIApplicationTools appTools, String targetFileNonSilverlightAssemblies)
   at DnDotNet.Parser.Resources.XamlResourceContainer.Parse()
   at DnDotNet.Parser.Resources.AssemblyResource.ParseAssemblyDefinition(AssemblyDefinition currentAssemblyDefinition, Dictionary`2 missingResources, Boolean handleSatelliteAsMain)

I tried adding a "dummy" string to the resource table in the DLL, thinking perhaps Passolo was getting confused by the fact that there were no regular strings in the table, but this didn't help.

What does this mean, and how can we fix it ? Should we open a support case ?

Thanks for any assistance !

-Rob

Regd Passolo 2009 -> 2022 migration , Issue faced

SHARADKUMAR JAYAKUMAR — Fri, 22 Nov 2024 11:37:38 GMT

Hello RWS team,

We are currently migrating the projects of our legacy environment from Passolo 2009 to Passolo 2022. However, we've noticed that Passolo 2022 is not parsing all the strings from resources that are still compiled with .NET 3.5, which is blocking translations for our C# applications.
In this migration test, we opened our Passolo 2009 projects in Passolo 2022 converting them to the latest format. Then, Passolo won't generate dlls without updating the strings. We get the following error message:

ERROR - Parser Error:System.Exception: Resources are in Passolo 2009 format. Update project before generating target file.

When we update the project, Passolo still correctly recognizes the source strings, but the strings of the target language are significantly reduced as most of the dialogs were not parsed.

Is there a missing step or does Passolo 2022 not support .NET 3.5 source files? Is there a better way to handle .NET 3.5 resources?

If Passolo 2022 does not support .NET 3.5, is there a version of the software available to work with such resources?

--------------------------------------------------------------------------------

Response from Passolo support

Passolo 2022 does support .NET 3.5 resources, but the processing of files has changed since Passolo 2009.

I've checked your project, and I do notice a bunch of target strings being removed. This is caused by Passolo hiding non-localizable forms. I think certain dialogs are not marked as localizable in Visual Studio.

You can change the parser to not hide such forms from the String List Settings > Parser > Setup > Parser option > untick the option Hide non-localizable forms.

After this you can update both the source and string list and these forms will not be hidden, including their strings. You might also want to check this with the developer, if these dialogs should be translated, they should be marked as localizable in Visual Studio.

Note that you can also unhide the dialogs from Passolo > Source list > Select the dialog with the gray circle then in the Properties Window (Bottom right side) Clear the Hide box and update the Target string lists.

Let me know if this helps or if you require further assistance.

Kind regards,

Adrian Maniu

----------------------------------------------------------------

WE have tried the workaround mentioned but there is no remedy. Is there any step missing. Attaching the screenshot

Passolo 2009 to Passolo 2022 upgrade

Vanjipriya V — Thu, 21 Nov 2024 12:43:59 GMT

In passolo 2009, resources compiled with .Net 3.5 is working. When we moved to Passolo 2022, we are facing an error saying "Resources are in Passolo 2009 format. Update the project before generating target file"

BAML strings that contains markup are not visible in Passolo

Cristian Galindo — Wed, 09 Oct 2024 08:23:00 GMT

In the XAML definition of a .NET 8 WPF control there is a TextBlock, it contains a piece of text that is enclosed in markup for bold effect:

After the dll is imported in Passolo 2022 Professional Edition 22.0.116.0, only the text outside the bold markup is recognized as part 0 and part 2, therefore only them can be translated:

what should i do in order to be able to see the missing string in Passolo?

XAML/BAML localization

Franz-Josef Knelangen — Mon, 12 Aug 2024 09:38:13 GMT

Passolo 2022 (22.0.207) can render BAML in a way but doesn't find any translatable strings. Is there a way to make the rendered strings available in Passolo?

Unable to update :NET8 dlls

Andreas Ternes — Fri, 05 Jul 2024 05:52:20 GMT

Hello,

after an update in the development environment (.NET6 -> .NET) I am no longer able to update the source text lists in Passolo 2022 (2022.0.193.0 witt .NET-AddIn). I get the following error message:

Aktualisiere Quelltextliste - BLMasterActionProtocolResx
Warnung - DotNetCoreManager cannot load DotNetCore COM server
Die COM-Klassenfactory für die Komponente mit CLSID {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} konnte aufgrund des folgenden Fehlers nicht abgerufen werden: 80008096 Ausnahme von HRESULT: 0x80008096.
FEHLER - Parser-Fehler:System.Exception: Parse
bei DnDotNet.Parser.Resources.AssemblyResource.Parse()
bei DnDotNet.Parser.WFParser.AppDomainRunner.Parse(String fileName, enmParsingTypes action, CPAICustomFile customFile, CPAIAddIn addin, CPAIApplicationTools apptools)
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei ReflectionHelper.DotNetHelper.PrepareFramework(String fileName, IBamlManager bamlParserAppFactory, FrameworkVersionStore verInfo)
b

Microsoft .NET8 SDK 8.0.302 incl. :NET Desktop Runtime 8.0.6 are installed. Is the problem with my environment or with Passolo? What can/must I do so that I can continue working?

Thanks in advance

Andreas

Ho to get "Referenced Assemblies" in translator packages so that the translator sees the correct UI?

Franz-Josef Knelangen — Mon, 01 Jul 2024 10:26:02 GMT

Our project has several 3rd party dlls that are not localized but used for resolving, rendering... In Passolo you can copy them to a subfolder named "Referenced Assemblies" and they will be used but not added to the translation list.

Opening a DLL in Passolo (full version) renders the UI OK. Exporting the project for translator's edition doesn't. I tried to add these DLLs as "user files" in the package, but it didn't help.

How can I add these DLLs so that our translators can see the correct UI during translation?

With "Show resource" icon I can't see the whole content of the dialog and have no access to the text boxes

Thomas Janowicz — Thu, 02 May 2024 09:10:13 GMT

Hi all,

we have big problems after updating Passolo 2022 with the Update CU3. We are loading dll files and using the .NET parser.

With the "Show resource" icon I can't see the whole content of the dialog belonging to a text box and I have no access to the text box. E.g. I can't change the position or the width. Mostly I see only the frame of the dialog or only some text boxes without any possibility to edit the box.

Also after generating the language dlls and loading them into our software, some content of the dialogs are shifted to the right for the languages, so you can't see the whole content of the dialogs.

With the un-updated Passolo 2022 everything works fine.

Perhaps our problems have something to do withn the .NET parser changes by Passolo?

There should be so much more text boxes!

The \update \generate command works differently to generating target files manually.

Pawel Pietrzak — Thu, 11 Apr 2024 10:23:57 GMT

Hi,

I have a problem using passolo 2022 (22.0.193.0).

When I create target files manually in my application, everything works fine (for all translated languages), but when I do \update and \generate using script during pipeline, I get an exception after starting my application (in all translated languages except the default language). I'm sure it's not a problem in the code because with the previous version of Passolo everything worked fine, the problem appears after upgrading Passolo to the latest version.

System.ArgumentOutOfRangeException: Value of '0' is not valid for 'SplitterWidth'. 'SplitterWidth' must be greater than or equal to 1. Parameter name: SplitterWidth at System.Windows.Forms.SplitContainer.ApplySplitterWidth(Int32 value) at System.Windows.Forms.SplitContainer.EndInit() at WSCad.UI.Forms.WSContactorManagerForm.#0j() at WSCad.UI.Forms.WSContactorManagerForm..ctor(IWSBauteil selectedItem, Boolean isSelectionMode)

Could someone please help me troubleshoot this issue?

Any insights or suggestions would be greatly appreciated.

Thank you!

Pawel

Unable to update source lists after switch to .NET 6

Andreas Ternes — Mon, 11 Dec 2023 10:11:32 GMT

Hi, I'm no longer able to update my source lists after our dev team switched to .Net 6/Core. I'm using Passolo 2022 with .NET Add-in, but the update shows only eror messages. The necessary .NET runtime is installed.

Aktualisiere Quelltextliste -ExampleResx
Warnung - DotNetCoreManager cannot load DotNetCore COM server
Die COM-Klassenfactory für die Komponente mit CLSID {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} konnte aufgrund des folgenden Fehlers nicht abgerufen werden: 80008083 Ausnahme von HRESULT: 0x80008083.
FEHLER - Parser-Fehler:System.Exception: Parse
bei DnDotNet.Parser.Resources.AssemblyResource.Parse()
bei DnDotNet.Parser.WFParser.AppDomainRunner.Parse(String fileName, enmParsingTypes action, CPAICustomFile customFile, CPAIAddIn addin, CPAIApplicationTools apptools)
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei ReflectionHelper.DotNetHelper.PrepareFramework(String fileName, IBamlManager bamlParserAppFactory, AssemblyDefinition assemblyDefinitio

Do I need anything else to be able to update the source lists or do I have to make some settings for the .NET Add-in?

Add Microsoft parser add-in to licence?

Michiel Verfaillie — Thu, 19 Oct 2023 09:50:36 GMT

Microsoft net parser add-in is not working anymore since U upgraded to Passolo 2022.

How do I activate this add-in? I read that this add needs to be added to the licence. But how can this be done? Thank you in advance!

How the .NET Parser differentiates String Table and Dialog.NET

Florian Sitterle — Wed, 30 Aug 2023 07:34:00 GMT

Hello Everybody :),

I'm facing a weird behaving of Passolo 2022.
When i'm updating a dll sometimes it detect me a ressources from a class as a String Table , and sometimes as a Dialog.NET.

When he's switching from String Table from Dialog.NET it deletes all existing texts in string table related to the class to create them as a Dialog.NET.

I would like to know how the .NET parser differentiates String Table and Dialog.NET. How do he detect that the ressources is a String Table or a Dialog.NET

Many thanks.

Best regards,

Florian.

When using .Net Parser to process xxxx.resources.dll, the error message "ERROR - Main assembly for source satellite assembly not found" is displayed

Jerry H — Sat, 06 May 2023 08:33:59 GMT

When using Passolo's .Net Parser to process xxxx.resources.dll, is it necessary to have the main assembly xxxx.dll file?

ERROR - Main assembly for source satellite assembly not found. ver. 22.0.74.0

jiashuo Tian — Sat, 06 May 2023 08:06:18 GMT

When using Passolo .Net Parser to process xxxx.resources.dll file, an error message is displayed: ERROR - Main assembly for source satellite assembly not found. After researching online, we found that in order for Passolo to successfully process xxxx.resources.dll, the xxx.resources.dll file needs to be located in the same directory or a subdirectory of xxx.exe/xxx.dll. We would like to discuss this issue with experts and find out if the latest version of Passolo can handle xxxx.resources.dll files without the main assembly being present when using .Net Parser.

.NET add-in parser Error:HandleResource

Florian Sitterle — Wed, 19 Apr 2023 12:49:51 GMT

Hello,

Recently we tried to translate all dlls from our Software with Passolo professionnal edition 22.0.116.0
We try in different way : Batch (using pslcmd.exe) and through the HUD of Passolo.

Unfortunatly the .NET parser is throwing an Error saying : ERROR - Parser Error:HandleResource error: Heo.ExplorateurProjet.Vue.Forme.WelcomeScreen.WelcomeScreenForm

The problem is that it doesn't generate the resource's dll Heo.ExplorateurProjet.Vue because he encountered this error.

There is also no clue about this problem , i retrieved some log from the update and also the generation (both in attachement or below) but we found nothing.
I also checked the SDK installed version of .NET on the machine that translate, we have the 6.0 installed.

We would like to know why the parser is throwing an error and if it's possible to generate the resource's dll even if there is an error (the dll will contain normally only what could have been treated or translated before/after the error). Is there any possibility to get more detailed logs of the error?

Error In Generation :

Generating "Heo.ExplorateurProjet.Vue:French (France)"
Source file has issues. See diagnostic report for more details.
Warning - 82 strings could not be found in the translation list:
- String "_labelControlProjectName.Appearance" in Dialog.NET "Heo.ExplorateurProjet.Vue.Controle.WelcomeScreenProjectsListItem" ""
- String "_heoRibbonControlAdv.SearchEditItem" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" ""
- String "_heoRibbonControlAdv.SearchEditItem.AccessibleName" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" "Search Item"
- String "_barButtonSettingsSavingAndRecoveryOptions" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" ""
- String "_barButtonSettingsSavingAndRecoveryOptions.Caption" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" "Saving and recovery options"
- String "_barButtonSettingsSavingAndRecoveryOptions.AccessibleName" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" "toolStripButtonOptionEnregi..."
- String "_barButtonSettingsCatalogGuide" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" ""
- String "_barButtonSettingsCatalogGuide.Caption" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" "Catalog guide"
- String "_barButtonSettingsCatalogGuide.AccessibleName" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" "_toolStripButtonParametrage..."
- String "_barButtonSettingsUpdateData" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" ""
- String "_barButtonSettingsUpdateData.Caption" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" "Update Data"
- String "_barButtonSettingsUpdateData.AccessibleName" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" "_barButtonSettingsUpdateData"
- String "_barButtonSettingsGeneralOptions" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" ""
- String "_barButtonSettingsGeneralOptions.AccessibleName" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" "toolStripButtonGeneralOptions"
- String "_barButtonSettingsGeneralOptions.Caption" in Dialog.NET "Heo.ExplorateurProjet.Vue.ExplorateurProjetMenuRubanVue" "General options"
- String "_tlpMain" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectLabelForm" ""
- String "_hbpButtons" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectLabelForm" ""
- String "_tlpProjectDescription" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectLabelForm" ""
- String "_labProjectDescription" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectLabelForm" "Description"
- String "_textBoxName" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectNameForm" ""
- String "_labelName" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectNameForm" "ProjectName"
- String "_labelDescription" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectNameForm" "ProjectDescription"
- String "_textBoxDescription" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectNameForm" ""
- String "_tlpMain" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectNameForm" ""
- String "_tlpProjectDescription" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectNameForm" ""
- String "_tlpProjectName" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectNameForm" ""
- String "_hbpButtons" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChangeProjectNameForm" ""
- String "_imageComboBoxEditEtatProjet" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixEtatProjetForm" ""
- String "_tlpMain" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixEtatProjetForm" ""
- String "_tlpStatus" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixEtatProjetForm" ""
- String "_labelStatus" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixEtatProjetForm" "Status"
- String "_hbpButtons" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixEtatProjetForm" ""
- String "_imageComboBoxEditEtatProjet.Properties.Appearance" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixEtatProjetForm" ""
- String "_imageComboBoxEditEtatProjet.Properties.Appearance.Buttons1" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixEtatProjetForm" ""
- String "_imageComboBoxEditEtatProjet.Properties.Appearance.Buttons6" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixEtatProjetForm" ""
- String "tableLayoutPanel1" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixRepertoireForm" ""
- String "_tlpFolders" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixRepertoireForm" ""
- String "_hbpButtons" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixRepertoireForm" ""
- String "_heoBaseButtonsPanel" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.CollaborationGroupsManagement.EditCollaborationGroupForm" ""
- String "_heoBaseButtonsPanel" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.CollaborationGroupsManagement.CreateCollaborationGroupForm" ""
- String "_heoBaseButtonsPanel" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.CollaborationGroupsManagement.ShareProjectForm" ""
- String "_comboBoxNetworkCalculations" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.NetworkCalculationChoiceForm" ""
- String "_labelCountry" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.NetworkCalculationChoiceForm" "label1"
- String "_tlpMain" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.NetworkCalculationChoiceForm" ""
- String "_hbpButtons" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.NetworkCalculationChoiceForm" ""
- String "_tlpCountry" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.NetworkCalculationChoiceForm" ""
- String "_textBoxName" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.NewProjectForm" ""
- String "_labelName" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.NewProjectForm" "label1"
- String "_labelDescription" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.NewProjectForm" "label2"
- ...
Warning - 5 strings did not use the translation, because the source file has changed text or coordinates.
- (40) String "_labelTitre" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.ChoixRepertoireForm"
- (1321) String "$this" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.CollaborationGroupsManagement.Base.CollaborationBase"
- (250) String "_labelTexteRechercheSur" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.RechercherProjetForm"
- (245) String "_labelTexteMotCle" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.RechercherProjetForm"
- (284) String "label1" in Dialog.NET "Heo.ExplorateurProjet.Vue.Forme.LancementDictionnaireForm"
ERROR - Parser Error:HandleResource error: Heo.ExplorateurProjet.Vue.Forme.WelcomeScreen.WelcomeScreenForm
Generating "Heo.ExplorateurProjet.Vue:German (Germany)"
Source file has issues. See diagnostic report for more details.

Log Update :

Resource: Heo.ExplorateurProjet.Vue.Forme.WelcomeScreen.WelcomeScreenForm.resources

    Inheritance Path:
        Heo.Systeme.BaseApplication.Vue.Forme.HeoBaseModalForm.resources (root, external)
    
    Root class type is Form
    Root class type hint from resource data is Form
    Resource Reader Scheme: Framework1X, Framework2X
    
    Missing or Erroneous References:
        Heo.Systeme.BaseApplication.Vue, Version=6.0.2304.1804, Culture=neutral, PublicKeyToken=null
            Heo.Systeme.BaseApplication.Vue.Controle.HeoCloseFormButton (Unresolved)
            Heo.Systeme.BaseApplication.Vue.Controle.HeoSecondaryButton (Unresolved)

Thank you very much.

Best regards,

Florian.

.NET add-in parser not loaded in Passolo 2022 (v22.0.116.0)

Andrea Zancan — Thu, 24 Nov 2022 15:04:54 GMT

hello,
I've a problem about loading the .NET parser add-in: Passolo 2022 reports the add-in is not loaded, even if the add-in is part of my license, like you can see on attached screenshots.

Please note all worked fine since few days ago!

Below is my Passolo 2022 add-in dialog:

This is the About dialog:

This is my account order information:

thanks

bye

Set culture property in Passolo?

Yvonne Rezbach — Fri, 18 Nov 2022 15:09:15 GMT

Hello,

development told me that my translated dll fils (parsed with Michrosoft .NET parser as usual) all had the attribute culture = neutral instead of the language. The language attribute is, howevver, set correcly:

All other projects work, also from this customer and I don't recall having changed anything *but the target path rules* (which, Ihoped, changed only exactly that ;:-))

I don't see the culture in the version strings either (which I ususally lock for translation)

Is there a way to change this property in Passolo at all or do you think the issue might be with the source files?

UWP: translation possible?

Franz-Josef Knelangen — Mon, 12 Sep 2022 13:01:34 GMT

Hi there,

I got this form one of my developers:

---

In a WPF application a user control „XamlHost“ is added using the NuGet packet „Microsoft.Toolkit.Wpf.UI.XamlHost“.

Inside of this „XamlHost“ UWP user controls are added by defining the appr. InitialType.

The „XamlHost“ functions as a wrapper for inserting UWP user controls into WPF applications.

---

Importing a DLL containing such a form into Passolo I get a window with this control as string but no localizable content.

Any idea how to handle this?

Thx,

Franz-Josef

Superscript character not exported to XLIFF

Yvonne Rezbach — Tue, 17 May 2022 10:32:03 GMT

Hello,

I'm using Passolo professional 18.0.178.0

My dll source file contains a character for square millimeters, which is displayed in Passolo as folows:

Text properties editor:

string overview editor:

History:

This character is not exported to xlif, i.e. not translated / reimported properly (just left out it seems:

this is my current parser setting:

Does anyone know what kind of character that is and whether it's an issue of the source file's encoding or parsing or... Where should I start investigating? ;-)

(BTW: I used a freeware tool to look into the DLL file but even there I don't see the superscript 2., just not displayed...)

Thank you! :-)

yve

WPF Custom control not rendering in Passolo 2022 Demo version

Siby Philip — Wed, 16 Feb 2022 15:46:58 GMT

Hi All,

The sample application created with a custom control are not rendering in Passolo.

seeking help, please advise me.