Home/ Questions/Q 1957986
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T07:57:22+00:00

I have a class/library project I made in Visual Studio, a Spreadsheet in the

  • 0

I have a class/library project I made in Visual Studio, a Spreadsheet in the SS namespace. Next, I created a windows form application, I then added the DLL, and put it in my resources menu, and it builds just fine, however, at runtime, I get a TryLoadException, which the documentation seems to say means it’s not in the assembly, but then why does it compile just fine? Also, I doubt it is a problem with my DLL, as my friend made a similar DLL (matching the same APIs, but built differently, and it works for his Windows Forms application), and I still get the TryLoadException.

Here is the procedure I followed.

  1. Create (and implement) the spreadsheet class.
  2. Create a new solution and project for the spreadsheet gui.
  3. In the project, right click and add an existing item, the dll found in the first solutions bin/debug (or bin/release, I tried both) folder. Also added the dll to the references.

  4. Somewhere in the code that get’s executed, add the line:

    Spreadsheet ss = new Spreadsheet(); // They’re both in the same namespace already

  5. Build, note that there are no errors.

  6. Run, execution stops right there with the TryLoadException.
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You put the DLL in your resources menu? That seems really strange.

    Some things to try. First, after the build, go and look in the Windows Forms project’s Debug (or Release, whichever you are about to run) folder. You should see your exe there and also this DLL you need. If not, there is a problem with the way you set the reference, such as not having CopyLocal or something else.

    Second, if your DLL and your Windows Forms app are projects in the same solution, use a Project Reference instead of browsing to the DLL. This will make life a little simpler.

    Third, try double-clicking the exe instead of pressing F5 and see if that affects anything. (The current directory is different in these two cases which is often relevant when trying to find DLLs.)

    Fourth, try removing the reference, taking the DLL away from Resources or whatever strange place it is now, and adding the reference again. See if things behave better then.

    • 0