Letters from Readers

Reader Feedback: Dev Disasters, Extend Classes

We rounded up readers' development misadventures for the December 2012 cover story, "Dev Disasters -- Why They Happen, How to Overcome Them". No surprise, when projects go horribly wrong, it's entertaining -- as long as it's not happening to you!

Great stuff! IMO, you can leave out the code snips -- the last thing I want to do is search the author's code for bugs when I have my own to debug. Just articulate the problem, those stories are way more entertaining ...

Name Withheld, Posted Online

Please keep the Dev Disasters column going!! I love reading these stories! Excellent stuff!!!

Name Withheld, Posted Online

Try This Extension
VSM Tools Editor Peter Vogel hates making changes to working code. He shared another method in his Dec. 3, 2012, .NET Tips and Tricks blog, "Extend Classes Without Changing Code".

Thanks! I never knew this existed. It seems like it would best be used where source code isn't available (purchased DLL, for example). If source is available, I would add the method to the base class. If you don't want to risk an expansion of changes to the original source, you can use a separate source file and make it a partial class.

Name Withheld, Posted Online

About the Author

This story was written or compiled based on feedback from the readers of Visual Studio Magazine.

comments powered by Disqus
Most   Popular
Upcoming Events

.NET Insight

Sign up for our newsletter.

Terms and Privacy Policy consent

I agree to this site's Privacy Policy.