Framework Design, Agile Coach, President Oklahoma City Developers Group, Microsoft MVP C#, TDD, Continuous Integration, Patterns and Practices, Domain Driven Design, Speaker, VB.Net, C# and Sql Server
Here’s a neat little thing about Visual Studio 2005 IDE for Visual
Basic.Net. When you implement the IDisposable interface, the
following code is automatically created for you. This is
different from other interfaces in that only the code stubs/shell (empty methods)
are produced for other interfaces. The auto-cdoe for IDisposable
actually produces the code needed for the entire implementation except
for the actual cleaning up of resources. The private fields,
Public Dispose Sub and Finalize come complete with no needed
modifications so that nothing gets left out. However, if you
forget to clean up a managed or unmanaged resource in the Private
Dispose(bool) method, that's your own fault :). Update: As Blair mentioned in the comments, for C# IDE you can right click on the IDisposable term and pick if you want to explicitly
or implictly fill in the stubs for the interface.
About Raymond Lewallen
Working primarily in the public sector during his career, Raymond has designed and built several high profile enterprise level applications for all levels of the government. Raymond now works as a solutions architect for EMC. Raymond is an agile coach, Microsoft MVP C# and also president of the Oklahoma City Developers Group and Oklahoma Agile Developers Group. Raymond spends a lot of his time learning and teaching such things as Test Driven Development, Domain Driven Design, Design Patterns and Extreme Programming practices and principles, to name a few. Raymond is also an advocate of Alt.Net. Raymond is primarily a framework guy, so don't ask him anything about UI :)