... can be a problem. Make sure you know what you're doing.
In the recent article, Shadows in VB.NET, I write that "Shadows forces a specific element to be used even if an identically named element exists." But this behavior can be a problem. To use Overrides, the base element has to specifically authorize it with the Overrideable keyword. Shadows has no such restriction. That means that if a procedure is inheritable (Many aren't.) you can accomplish about the same thing with Shadows that you can with Overrides. A new Quick Tip shows how to do it. (And recommends against it.)