I confess,I don’t do a ton of VB.NET coding. Check that – I don’t doany VB.NET coding. I’m strictly a curly-braces-and-semicolons kind ofguy. However, I’m finding myself responsible for a code generator thatneeds to be bi-lingual between C# and VB.NET. As a result, I’m sort offorced to code VB by proxy…
Anyway, I wanted to toss out a question to the more VB-minded readers of thisblog: what are the best practices around setting the RootNamespace property inthe project options? On large projects, do you set this to something and omitnamespace declarations from the class files, or do you leave it blank anddeclare namespace membership explicitly, a la C#?
Personally, the whole RootNamespace feels like pure evil to my C# mind. Thethought that my class might actually not be in the namespace it declares seemsnefarious at best. I can see how this would be a valuable feature to a VB6developer who might be namespace-phobic, but I’m curious how this featuregets used on enterprise-level projects.
