2. .NET Add-In - Recent Threads

RE: How to enable Setup button

Balázs Fehér — Wed, 18 Jun 2025 07:36:32 GMT

Thanks for the quick reply! Setting the "init.Style" solved the issue

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.

RE: How to enable Setup button

Achim Herrmann — Wed, 18 Jun 2025 07:16:17 GMT

Your add-in must tell Passolo within the Initialize() Function that you are implementing the callback for a Setup function like

public override int Initialize(CPAIInit init, CPAIApplicationTools apptools, CPAIAddIn addin){… init.Style = enmPAIStyle.SetupData;

Later in the code, you need to implement the Setup() function itself like

public override int Setup(){}

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

Adrian Maniu — Fri, 13 Jun 2025 12:16:34 GMT

Hi Franz,

In order for Passolo to process DLL files it needs to run them, however this might not always work as your DLL's might depend on other DLL's being run before them.

This seems to be the case for image 1. I think the ReadSys.Load function is trying to access some data which does not (yet) exist or might even be from a different machine not accessible, depending on your application.

Such issues cannot be addressed by Passolo. The solution would be to not read data in the Load form constructor or the InitializeComponent() but instead use separate functions that run after the Constructor.

Additionally, the Constructor and the InitializeComponent() code should not be changed manually, use only the Visual Studio generated code.

Another advice is for Dispose() functions to check for null objects as your DLL might not have initialize certain objects and they can throw errors at Dispose().

I hope this helps.

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

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

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

Franz-Josef Knelangen — Wed, 11 Jun 2025 07:22:05 GMT

After quite a bit of back and forth with RWS support, we received a new beta version. Upon examining the stack trace, we discovered a reference to a .NET 9 (!) system DLL in the crashing project. After removing this faulty reference, the crash was resolved. Thank you, Adrian ♡. - Perhaps Passolo can catch this kind of error in the future.

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?

RE: Addin version does not appear

Balázs Fehér — Mon, 02 Jun 2025 06:02:41 GMT

Thanks for the information! Answer is not that simple, because those informations are defined, yet Passolo does not load such information. Will ask it on another forum.

RE: Addin version does not appear

Achim Herrmann — Mon, 02 Jun 2025 05:52:26 GMT

Yes, that might be the wrong forum for this question, as it is usually for users that are using the .NET add-in to localize .NET based software.

But the answer to your question is simple and not very complicated. Passolo plug-ins are DLLs and usually each development environment allows developers to define some Microsoft PE compatible Version resource in DLLs. The version information from the main plugin DLL is displayed here automatically.

RE: Addin version does not appear

Balázs Fehér — Mon, 02 Jun 2025 05:38:58 GMT

I am from Kaleidoscope, and I am looking for help on the dev community forum, since I haven't find anything in the SDK regarding this. I hope someone can specify what must be set to be able to display a version number there. Am I on the wrong forum?

RE: Addin version does not appear

Achim Herrmann — Mon, 02 Jun 2025 04:51:23 GMT

The Kalcium plugin for Passolo wasn't developed by RWS, so we cannot help answering this question. Please contact Kaleidoscope in Austria, which developed this special plugin.

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

Franz-Josef Knelangen — Mon, 19 May 2025 09:55:36 GMT

Thank you, Paul! Got your e-mail. That was quick!

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

Paul Filkin — Mon, 19 May 2025 09:14:57 GMT

Anna Franz We will be pleased to help you with this problem so have logged a support case on your behalf. We do prioritise customers who have a support contract so please keep in mind it could take up to 48 hours, especially over a weekend, but rest assured we will contact you as soon as we can. You will be contacted at the email address used for this Community. Support Case Id : CS0011586.

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

Franz-Josef Knelangen — Mon, 19 May 2025 09:08:15 GMT

We currently don't have a support plan - but I think one can submit exceptions/crashes of Passolo w/o such a plan, just can't figure out, how...

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

Achim Herrmann — Fri, 16 May 2025 05:57:43 GMT

Nothing that can be replied within this forum. This is definitely something that needs a deeper analysis by our support engineers. Please log a support case at https://gateway.rws.com/csm

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

Franz-Josef Knelangen — Wed, 14 May 2025 04:54:40 GMT

OK. Understood. Thank you!

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

Paul Filkin — Mon, 12 May 2025 08:52:50 GMT

Franz-Josef Knelangen

[quote userid="162549" url="~/product-groups/trados-portfolio/passolo/f/net-add-in/57719/psl-exception-parsing-source-files---after-project-update-containing-modularization-with-nuget-packages"]Response to Spam Filter: This is no spam. Don't know what triggered this. Greetings, Franz-Josef[/quote]

At a guess it's probably all the repetition in the text. It often helps to avoid this if you add this sort of content as a code block using the Insert Menu.

Just in case you need to do another one :-)

RE: Passolo 2022 Professional -- what does this error mean ?

Robert Yang — Tue, 18 Mar 2025 11:54:00 GMT

We opened a support case, but in the end due to schedule pressure had to just work around the issue by turning on localization for one of the Windows Forms controls involved and a few tweaks.

I think we learned that Passolo support for WPF might still be a bit lacking in places.

Good luck.

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

RE: Passolo 2022 Professional -- what does this error mean ?

Adrian Maniu — Tue, 18 Mar 2025 09:27:12 GMT

Hello, the issue here was caused by embedding XAML files into the DLL which Passolo tries process as Silvelight files.
As a workaround you should include the resources as BAML files which work fine in Passolo.

I think Robert Yang has better details about the workaround they applied for this case.

RE: Passolo 2022 Professional -- what does this error mean ?

Sunny Sun — Tue, 18 Mar 2025 02:44:23 GMT

Same problem😢, any solution or workarounds then?

RE: .NET parser add-in fails to load

Adrian Maniu — Fri, 31 Jan 2025 19:42:39 GMT

Hi Bernadette Haury , for licensing issues please raise a case for the support team:

https://gateway.sdl.com/CommunityKnowledge?articleName=000002535

.NET parser add-in fails to load

Arash Ansari — Thu, 04 Feb 2021 18:02:57 GMT

Hi Adrian Maniu

I have installed Passolo 2018 recently (pro edition) but it fails to load Microsoft .Net parser add-in:

"Requested feature is not available". Does this mean that there is an issue with my installation of Passolo? Or this add-in is not included in the pro edition? The add-in works find on the demo edition I have installed.