Placing custom code in a System namespace

Question

Are there any best-practices that state custom code shouldn\'t be placed in a System namespace? Should System and its children be reserved for Micr

Answer 1

If you place a new class in System.InteropServices, every file that has a using System.InteropServices; clause is forced to have your class in scope, which may confuse the programmer. Since the programmer cannot defend oneself against this, I'd consider this bad practise.