On the Assembly Information window, check Make assembly COM-Visible. This allows COM-based applications to call the class library's member variables and methods. There are a few ways to do it based on your circumstances.
Applications created in VB or VBA are COM-based applications. For a development machine, we can check "Register for COM Interop" setting in Visual Studio. Then check Register for COM Interop (Based on your version of Visual Studio, it could be on a different tab). Depends on whether your build is a Debug or Release build, you can find the DLL and type library file in either Debug or Release folder under the bin directory.
It is the same process you would use for creating an arbitrary portable config file not tied to any particular assembly, but for which you want to make use of .
NET's XML schema, config section and config element mechanisms, etc. This will cut you off from the version protection offered by the automatic path generation mechanism.
Net is not that hard as long as you have object oriented programming experience or knowledge.
Net DLL, and (3) how to correctly reference the DLL within Access VBA or Excel VBA.
For this reason, when you retrieve a Configuration object using the "normal" method, the object you get back is tied to the configuration of the App Domain you are executing in, rather than the particular assembly.
Peter 16Nov15: I spent some time this morning working on grouping of the digitalfishphones plug-ins.
I chose that set as this author's plug-in regulary occur on the forum posings (my memory tells me).
The App Domain is bound to the root assembly which loaded the assembly which your code is actually in. It is possible to spin up other app domains within an application, but you must explicitly provide information on what the root assembly of that app domain is.
In most cases this will be the assembly of your main . Because of all this, the procedure for creating a library-specific config file is not so convenient.