Alright, next question!

I'm writing a .DLL (class library), and have a main class (called "Plugin") that gets loaded by the external application. In this Plugin class I have a method that gets called from the external app called "Parse", I have a somewhat large ParseIncoming function in a module all by itself, in the same project as the main Plugin.vb. I also have another .vb file that represents another Class (called Settings), which is used by the Plugin class. In the Plugiin class, I define a new instance of my Settings class.

Now, the problem shows itself when I try to make use of my instance of the Settings class (called CurrentSettings) from the module file that the ParseIncoming function is in. Basically, the CurrentSettings class isn't recognized at all by this module. I think it has something to do with scope, but I'm not sure really. Here is a summary of what should happen:

Code:
Plugin.vb contains a "Plugin" class
Settings.vb contains a "Settings" class
Parsing.vb contains a module called "ParsingFunctions" which currently contains a procedure called "ParseIncoming"

The Plugin class creates a new Settings class instance.

During runtime:
1) Plugin class gets loaded by external app
2) Plugin class contains an instance of Settings class
3) External app calls Plugin.Parse()
4) Plugin.Parse calls ParseIncoming() from the seperate module
*5) The Parsing module's ParseIncoming() procedure can't access the Plugin class's instance of the Settings class
I want to rectify step 5, and allow my module to access the Plugin class's instance of the Settings class.


I hope this wasn't too long winded, and that it makes sense! Thanks in advance.

-Brandon