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