KnowledgeHub
Questions
Tags
Users
Search
Alex Rivera
|
Logout
Edit Question
Title
Body
I would find it convenient/logical to write my exensions for a class in a nested class. The main reason is I could simply name that class Extensions and let it's outer naming scope give it a unique type name for the compiler. What is the technical reason to disallow something like: public class Foo { ObjectSet<Bar> Bars { get; set; } public static class Extensions { public static Bar ByName(this ObjectSet<Bar> bars, string name) { return bars.FirstOrDefault(c => c.Name == name); } } } Whereas now I have to create a separate free standing class. Update/Note: I wasn't imagining that the fact it was an inner class would affect the scope of availability of the extension method. I only wanted to address the practical coding issue a separate class with a separate name.
Tags (comma-separated)
Save Edits
Cancel