[RESOLVED] DLL - Class or Module?

[techgnome]

Making a class and marking every public method static seems silly, no?

No, not really... because 1) that's what's going on behind the scenes anyways... 2) the concept of a module is VB-specific... C# doesn't have anything like it (short of doing it all by hand). So in general terms of learning OOD/OOP ... no, it doesn't seem silly, but logical. The use of a module file simply takes the mundane out of having to do it yourself.

-tg

[MarMan]

So tech, you think it makes absolutely no difference whether a module or a class with all its membres static is used? Or is it better to use the class since that is what it really is anyway?

[jmcilhinney]

the concept of a module is VB-specific... C# doesn't have anything like it (short of doing it all by hand).

A VB module is equivalent to a C# static class. If you declare a class static in C# then declaring a non-static member will produce a compilation error. The two compile to the same IL. The module concept in VB is in keeping with VB6 modules.