Is it good practice to call module functions directly in VB.NET?

Posted by froadie on Stack Overflow See other posts from Stack Overflow or by froadie
Published on 2010-04-29T14:36:43Z Indexed on 2010/04/29 14:47 UTC
Read the original article Hit count: 367

I have a Util module in my VB.NET program that has project-wide methods such as logging and property parsing. The general practice where I work seems to be to call these methods directly without prefixing them with Util. When I was new to VB, it took me a while to figure out where these methods/functions were coming from. As I use my own Util methods now, I can't help thinking that it's a lot clearer and more understandable to add Util. before each method call (you know immediately that it's user-defined but not within the current class, and where to find it), and is hardly even longer. What's the general practice when calling procedures/functions of VB modules? Should we prefix them with the module name or not?

© Stack Overflow or respective owner

Related posts about vb.net

Related posts about modules