Home/ Questions/Q 4116206
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T22:40:47+00:00

The program worked fine until I did this: Added a new class under an

  • 0

The program worked fine until I did this:

  1. Added a new class under an existing file and an existing namespace.
  2. Added settings to that project the new class belongs to.
  3. Build the solution.
  4. Build the setup project.
  5. Installed the new version on a machine.

When I start the new version on the machine, then I get:

Unhandled Exception:
System.TypeLoadException: Could not
load type
‘SI.AS.CommonLogic.Utils.ErrorLog’
from assembly
‘SI.AS.CommonLogic.ErrorUtils,
Versions=1.0.0.0, Culture=neutral,
PublicKeyToken=925c8734ae397609’. at
RSMonitor.RSMonitorMain.Main(String[]
args)

ErrorUtils is the new class I have added. There was a file with a static class in it. I added another static class under it and added settings to the project. It runs smoothly on my developer machine in debug mode. But I can’t install and run it on another machine. The program can call the other static class from the same file. What am I missing here?

** update **

I tried to install it for a 2nd time and checked the DLL. The timestamp matched the latest compiled version and now it works. I have no idea why it didn’t work last time, because it is the same package I installed again. But if I get same error, then I’ll try out your suggestions.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Your program looks like it is having trouble locating another assembly, probably called SI.AS.CommonLogic.ErrorUtils.dll. Either that, or it can only find the wrong version of this assembly.

    Is this an assembly that is part of your solution?

    If so, is it in the “bin” directory on the machines that it is failing to run on (in other words, is this assembly being deployed correctly with your app)?

    If not, is this a part of a seperately installed component or application that is installed on your machine but not on the others (ie is this an external dependency that is missing on the other machines)?

    One thing that may help here, is to use the Assembly Binding Log Viewer on both the miachine this does work on, and the machine it doesn’t to see where it gets loaded from in the working case, and where it is trying to load it from in the failing case.

    Note you may need to make a registry change to get this to log all assembly bin info:

    Set the HKLM\Software\Microsoft\Fusion\ForceLog registry value to 1 (the value is a DWORD).

    • 0