Question

This is a follow-up to my previous question Stop my "Utility" from giving errors between different architectures, suppose I am trying to create a class library that looks something like this:

- Class Utility (Parent class)
     ... Utility functions and methods
         (EG: Public Sub Sub1() )

  - Class Utility_Web
       ... Functions and methods only related to Web / Web-Controls
         (EG: Public Sub Web_Sub1() )

  - Class Utility_WinForms
       ... Functions and methods only related to Winforms / WinForm-Controls
         (EG: Public Sub WinForm_Sub1() )

Now, what I would like to be able to do is to just add the Utility dll as a reference to any of my projects and be able to access the functions and methods from ALL 3 of these classes by simply typing in, for example:

Utility.Sub1
Utility.WebSub1
Utility.WinFormSub1

In other words, not having to type:

Utility.Utility_Web.Websub1

And making it so that the end-programmer doesn’t need to know the internal structure of this utility, they can reference all it’s methods / functions with just the Utility. nomenclature.

How would I go about doing that? Is this where NameSpaces come into effect? Inheritance? Partial Classes? Modules rather than classes?

Answer 1

There doesn’t seem to be any reason for these methods to be in separate classes if they are going to be accessed using the same class name.

If you want to split the code across many source files for organizational purposes, you can use partial classes.