The using Directive is a namespace alias (of which I was referring to)
The using Statement defines a scope at the end of which an object will be disposed (of which you were referring to)
The point I'm making is to stay away from aliases as much as possible (just check out the header to almost all C# code. You'll see using System; at the front of nearly every file. That's just an alias that does not affect bytecode, but makes the code less clear.
Regards...
It's easy to abbreviate code with lots of Using statements. However, this obfuscates code, since there are several thousand classes scattered across numerous namespaces. Plus there's no different in byte code between explicit naming and abbreviated naming combined with Using statements.
In our group, even the folks originally opposed to all that extra typing have now adopted this style, just for readability.
One more thing: After using doxygen for the past year, I view Microsoft's xml tags a distant second. The latest doxygen 1.3 candidate does a fairly decent job with C#, and the resulting documentation is much more informative than Microsoft's.
Just my two scents...
Slashdot Mirror
The point I'm making is to stay away from aliases as much as possible (just check out the header to almost all C# code. You'll see using System; at the front of nearly every file. That's just an alias that does not affect bytecode, but makes the code less clear. Regards...
It's easy to abbreviate code with lots of Using statements. However, this obfuscates code, since there are several thousand classes scattered across numerous namespaces. Plus there's no different in byte code between explicit naming and abbreviated naming combined with Using statements. In our group, even the folks originally opposed to all that extra typing have now adopted this style, just for readability. One more thing: After using doxygen for the past year, I view Microsoft's xml tags a distant second. The latest doxygen 1.3 candidate does a fairly decent job with C#, and the resulting documentation is much more informative than Microsoft's. Just my two scents...