Lol didnt see Trent already answered you. I agree about modules.

1)  If you reference your project from another project, whether VB or C#, the module routines aren't accessible even if they're public.

2)  You can name a local method in a class the same as a public module routine, and the compiler won't say anything about it.  When you use the method, the compiler won't require you to prefix it; it'll just happily use the local version instead of the module with no warning.

Shared classes, on the other hand, are accessible to outside projects (if you want them to be), and shared classes avoid the ambiguity because of the prefixed class name.

Thanks Trent. Thanks Paul.

Trent, How is a shared class different from a regular class?

Mike,

Your class is public but the module isn't so it is letting you know that your class is public which exposes the module which is friend. Just make the module public and it should work. Or make the class friend

Public module whatever

Paul

Since your enum and module have not been defined as public then you cannot have a public property expose those privately typed classes.  You need to add Public in front of Module and your enum.

I do not recommend using modules!  This was left for backward compatability.  You should use shared classes.  In the case of your enum, just move it outside of the module and it will reside as its own public enum:

Here is the error i'm getting:

'ParentFormID' cannot expose type 'Module1.ParentFormIDEnum' outside the project through class 'MyClass'.

Here is the related code:

I'm not sure what this error means. All I'm trying to do is create a global enum and be able to use it in all areas of my program.