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

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

jiashuo Tian

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.
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hello Tian,
    Please note that we found this error as well that is not related to the issue from Achim.
    For speed and completeness for multiple versions of the same assemblies (v1, v2, v3, etc), we make copies of the previous version, have it scan the new version files and then translate them.

    There is a bug in the software that if you do this way, you cannot change projects to another version of the same assembly names and then output those satellite assemblies. Changing the project doesn't load the assemblies of the new project. It caches the project right before it. That cache doesn't associate the assembly to these satellite assemblies, so it gives an error.

    To fix this error, we have to close Passolo every time we switch projects (version change), and then open only that project, output the satellite assemblies and then close Passolo again to move to the next project.

    This might not be your error, but if the answer from Achim doesn't fix it this might.
    emoji
Reply
  • 0

    Hello Tian,
    Please note that we found this error as well that is not related to the issue from Achim.
    For speed and completeness for multiple versions of the same assemblies (v1, v2, v3, etc), we make copies of the previous version, have it scan the new version files and then translate them.

    There is a bug in the software that if you do this way, you cannot change projects to another version of the same assembly names and then output those satellite assemblies. Changing the project doesn't load the assemblies of the new project. It caches the project right before it. That cache doesn't associate the assembly to these satellite assemblies, so it gives an error.

    To fix this error, we have to close Passolo every time we switch projects (version change), and then open only that project, output the satellite assemblies and then close Passolo again to move to the next project.

    This might not be your error, but if the answer from Achim doesn't fix it this might.
    emoji
Children
No Data