Hi BH,
It would look something like this:
sealed class Utilities
{
private Utilities(){}
public static void UtilitySubOne(string arg)
{
// blah blah
}
...
}
In other words, VB modules are implemented as sealed classes with a
private constructor where all the members are static. I think that VB also
promotes the member names into the global namespace, which means you can
type:
...
UtilitySubOne("foo")
...
instead of:
...
Utilities.UtilitySubOne("foo")
...
The former isn't something you can do in C#.
Regards,
Dan
"BH" <bo*****@yahoo.com> wrote in message
news:u7**************@TK2MSFTNGP09.phx.gbl...
Hi
what would be the C# equivalent of a VB.NET file that looks like this:
Module Utilities
Public Sub UtilitySubOne ( ByVal arg As String)
// blah blah
End Sub
Public Sub UtilitySubTwo ( ByVal arg As String)
// blah blah
End Sub
End Module
...VB.NET has the concept of a 'Module' where you can create a pile of
generally available calls, but I'm not sure how this 'Module' file idea
translates to C#.
Any help appreciated,
BH