Common Odds and Ends
I'm feeling more and more as if I need to put some common functionality into a project and use it from all my projects. This post is mainly for myself, but I would love to have some comments about the idea. It's not new or anything like this, but using .Net 2.0 features does allow for some intriguing possibilities. I've plenty of ideas that just spring to mind, some of them I blog about, but I don't get to use them, or I need to duplicate the effort. I'm not talking about big things, but about the small stuff that we need to duplicate so many times.
Here is the list of what I think I can put there right now:
- DisposableAction
- Date & Time Utils - It's amazing how often I need to do things with those that aren't supported.
- For Each day / week / month in range.
- Explicit Date Range
- Combing Date's Date and a Date's Time
- Parameter Validation:
- IsNotNull
- IsInRange - For Dates & Numbers.
- IsNotValue
- ValidDateRange
- Collection Utils:
- First
- Last
- SelectAll
- SelectAllNot
- Delegate Iteration
- Actionable Objects - Similar to the way NHibernate Generics works:
- Collections: Action on Add/Remove
- Values: Action on set
- Static Reflection - Because just having all the Func overloads will be great
- Property Indexer
Each of those is a small piece of funtionality, and while I like the thought of putting it all in one project, I don't know if they deserve a seperate project and seperate treatment, since they are actually quite small tidbits. Anyone can think of anything else that they might want to see there?
Comments
Comment preview