systemlordanubis
New member
- Joined
- Aug 6, 2018
- Messages
- 2
- Programming Experience
- 10+
Hi,
I would like to understand what methods might be possible to solve this scenario...
Let's say, I have a primary class library "classmain.dll" and a secondary library "classsec.dll".
Within "classsec.dll", I have a public method "checkstatus()" which performs some work. In the "classmain.dll", I have another method(s) which reference or call "checkstatus()".
However, what I would like to do, in some instances, is not include "classsec.dll" with the application (as perhaps its an additional module the client optionally needs to pay for); yet, unless I explicitly reference "classsec.dll" in the project, I can't compile "classmain.dll".
What I would like to achieve is to be able to alias (or similar) the "checkstatus()" method within "classmain.dll" such that I can handle an appropriate error response if "classsec.dll" is missing; but, if "classsec.dll" is present when the application is run, then it would utilize that method in place of the aliased version in "classmain.dll".
Hopefully, that explains the situation clear enough.
Thanks
Anubis
I would like to understand what methods might be possible to solve this scenario...
Let's say, I have a primary class library "classmain.dll" and a secondary library "classsec.dll".
Within "classsec.dll", I have a public method "checkstatus()" which performs some work. In the "classmain.dll", I have another method(s) which reference or call "checkstatus()".
However, what I would like to do, in some instances, is not include "classsec.dll" with the application (as perhaps its an additional module the client optionally needs to pay for); yet, unless I explicitly reference "classsec.dll" in the project, I can't compile "classmain.dll".
What I would like to achieve is to be able to alias (or similar) the "checkstatus()" method within "classmain.dll" such that I can handle an appropriate error response if "classsec.dll" is missing; but, if "classsec.dll" is present when the application is run, then it would utilize that method in place of the aliased version in "classmain.dll".
Hopefully, that explains the situation clear enough.
Thanks
Anubis