Module VS Class

Hey guys,

I'm building a web application in ASP.NET (..), and have to request quite a few values from cookies. Now, you can't peform any of the Request commands in classes, can you do that in modules?

If not, why should I use a module instead of a class?  Look's like they're the same so.. Cause now I have to redirect clients to tons of pages, because they need the QueryString, wich is not really secure and stuff.

So, what is the difference between a module and a class.

Diep-Vriezer wrote: So, what is the difference between a module and a class.

NET Framework SDK wrote: Modules are a reference type similar to classes, but with some important distinctions. The members of a module are implicitly Shared and scoped to the declaration space of the standard module's containing namespace, rather than just to the module itself. Unlike classes, modules can never be instantiated, do not support inheritance, and cannot implement interfaces. A module can only be declared in a namespace and cannot be nested in another type. You can have multiple modules in a project, but members with the same name defined in two or more modules must be qualified with their module name when accessed outside of their module.

cya,

/PatrikB

So if i understand good...
I ALWAYS have to do this when I use a module:

module1.test()

There is no way to import something (module1) that I just can use test() ?

I use this in such cases:

Dim MyClassRefferer As New MyClass

EDIT: I should have read your question better, this will still have the MyClassRefferer.Test() req. Use Imports MyClass instead, as described above.