In order to get round VB
2005's inability to share source files, I have split my applications into a shared component (in a class library) and and 3 projects that will be compiled into three separate applications and which reference the class library.
All three applications use a module that contains a set of public variables, and rather than copy this module into each application, I'd like to share it as well.
So, I put it into the class library, but even with a Public statement on the module and its variables and subroutines, I can't reference it from the main app. IMPORT shows the classes in the class library (which include a couple of forms) but not the module.
If I convert the module to a class, I'll have to change every reference to each one of its variables from "variable" to "instance.variable", and the same for its methods. Is this the only way to do it?
If you have trouble working out what I'm trying to do...
The first app gets data from the user and saves it on disk
The second app reads the data in and does something
The third app reads the data in and does something else
Each needs access to the methods and class structures that store and manage the internal representation of the data.