topic Re: Running a dll From Another dll in .NET Forum

Running a dll From Another dll

mgorecki — Tue, 30 Jan 2024 15:45:11 GMT

I have a program that currently uses a sub to create part of a specific drawing.

I have a request to make a standalone program from that sub so users can run just that part of the program.

What is the best way to do this?

I would like the designer to have the ability to just run the standalone, but the original program should be able to run it as well.

I don't want to have it in two places as I don't want to have to update code in two different locations.

Thanks

Re: Running a dll From Another dll

ActivistInvestor — Tue, 30 Jan 2024 15:51:26 GMT

You should decouple your sub from the program that contained in and place in a separate assembly/project. Then you can reference it from the program that you removed it from as well as any other program that you write and want to use it with.

Re: Running a dll From Another dll

mgorecki — Tue, 30 Jan 2024 16:08:07 GMT

Hi, yes I was hoping for a method to use. I'm sorry I should have been more specific.

What would the command(s) be for program 1 to run program 2?

After thinking about it, could that "sub" code exist in a library so that other programs could access and use it?

Thanks

Re: Running a dll From Another dll

ThomasRambach — Tue, 30 Jan 2024 16:17:07 GMT

You could just make a CommandMethod in the first DLL so that the user can run a custom command to launch the application directly from within AutoCAD. Does it really need to be a standalone executable or can they launch from within AutoCAD?

Re: Running a dll From Another dll

mgorecki — Tue, 30 Jan 2024 16:23:06 GMT

Hi, I was hoping to have a sub of some kind in a library. This sub will be passed some items.

I want multiple programs to have access to this one sub located in a library.

I have been looking for:

1. How to create that loibrary part (is it a dll, or ?)

2. How does a program call that particular function from the library part?

Thanks

Re: Running a dll From Another dll

_gile — Tue, 30 Jan 2024 16:43:21 GMT

Hi,

From a standalone application (EXE) you cannot use the .NET API (you're stuck to the COM API).

IMHO, the simplest way would be defining a command (with CommandMethod attribute) from your 'sub' in the 'library' (DLL) so that you can netload this 'library' from the standalone application by invoking the NETLOAD command and launch your command.

You can see this example in the docs.

Re: Running a dll From Another dll

mgorecki — Tue, 30 Jan 2024 16:53:15 GMT

Hi, after reading the replies, I have been thinking that the "standalone" option would not be the best approach.

I am now thinking that I need to create a "library" that would contain a number of "subs" that I use frequently in many of my applications. Would that library be a .dll? If so, could I attach it as a reference to multiple programs so they could just call those functions normally and pass them the appropriate items?

Would I be able to do that by attaching the "library.dll" using References, like I would the AcDbMgd.dll?

Re: Running a dll From Another dll

_gile — Tue, 30 Jan 2024 16:59:11 GMT

The library have to be a DLL.

You simply add it as reference to your projects setting the "copy locale" to true. The library have to be in the same folder as your project assemby. If you deploy your application, you have to join the library in the same folder.

Re: Running a dll From Another dll

mgorecki — Tue, 30 Jan 2024 21:52:44 GMT

Hi Gilles, I'm going to try that. Thanks

Re: Running a dll From Another dll

mgorecki — Tue, 30 Jan 2024 22:16:44 GMT

Hi Gilles,

I've created a project "UtilitiesLibrary.dll" and in it I have some subs.

I created a new project, and in the references I added "UtilitiesLibrary.dll".

I made a call to one of the subs in the library, but it tells me that its not declared and may be inaccessable due to its protection level.

How do I get it to see the functions/subs in the library?

Re: Running a dll From Another dll

_gile — Wed, 31 Jan 2024 06:43:17 GMT

To be accessible, the classes and members of the library have to be 'public'.