• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 44 subscribers
  • Views 197 views
  • Users 0 members are here
Options
Related

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

Franz-Josef Knelangen

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

Error message stating 'The path is not of a legal form' with a stack trace showing various system and application methods.

Dialog box for generating target files with an error message in German stating 'Standard output file could not be set' and an OK button.

Dialog box for generating target files with an error message in German about an exception in 'RetrieveObjectFromAssembly' caused by 'AKG.Dike.AsmHelper.AssemblyHelper'.

Generated Image Alt-Text
[edited by: RWS Community AI at 8:47 AM (GMT 1) on 11 Jun 2025]
emoji
Rate translation
×
Suggest better translation
×
  • 0

    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.
    emoji