CODEWITHSUNDEEP
c#projects-and-solutionsmulti-project
Mike Q
Mike Q

Reputation: 23229

C# solution referencing a pre-built .exe

I have a project which is the core of our application. We build several DLLs and an EXE.

We then have custom projects which use pre-built core DLLs and EXE and add customisations/extra bits as required. These customisations are always DLLs, the core EXE is always used. The core DLLs/EXE are referenced by the custom solution.

I'm having a bit of a problem while debugging getting the custom DLLs to load. Because the EXE is pre-built we use one the projects as the startup project which points to the location of the EXE and the rest of the DLLs. However it then doesn't seem to the load the startup project DLLs.

How should I be setting my custom solution/projects up when the EXE is already built?

(NOTE: the custom DLLs provide components which are loaded reflectively from metadata if you're wondering)

UPDATE: Current approach is to have a post-build event in the "top-level" project of the custom solution which copies all the core DLLs and EXE into the bin/Debug directory. Then set that top level project as the startup project and point to the copied EXE in bin/Debug. It then finds the DLL because it is in the same directory as the EXE (along with all the others).

Upvotes: 1

Views: 507

Answers (2)

Hans Passant
Hans Passant

Reputation: 942197

Selecting a DLL as the startup project does not in any way guarantee that it actually gets loaded. That EXE you are using has to use Assembly.Load/From() to get the DLL loaded. At that point does the debugger step in and activate the break-points you set.

Easy to tell from the Debug + Windows + Modules window. If you don't see your DLL loaded in that window then nothing is going to happen. You'll need to find out what the exact configuration rules are for that EXE so that it will load the DLL you want to debug.

Upvotes: 1

Yuriy Faktorovich
Yuriy Faktorovich

Reputation: 68737

You can run the .exe, then attach Visual Studio Debugger to the process. Make sure the .pdb for your .dll is in the executing directory.

Upvotes: 0

Related Questions