Click here to Skip to main content
15,896,527 members
Articles / Programming Languages / C# 4.0

ReflectionHelper

Rate me:
Please Sign up or sign in to vote.
4.93/5 (31 votes)
6 Aug 2012CPOL4 min read 72.9K   2.2K   79  
This class makes getting MemberInfos easy, without the use of magic strings (so it is refactoring friendly) and also allows you to create delegates to do fast accesses to those items, much faster than the normal Invoke, GetValue or SetValue methods.
using System;
using System.Collections.ObjectModel;
using System.Reflection;
using System.Linq.Expressions;

namespace Pfz.ErrorHandling
{
	/// <summary>
	/// Class that groups errors instead of letting the first one throw an exception.
	/// It has methods to start the packing (and disposing it stops the packing),
	/// methods to add errors, remove and clear errors (in case you know how to deal
	/// with them).
	/// </summary>
	public static class ErrorPack
	{
		[ThreadStatic]
		internal static _ErrorPack _current;
		
		/// <summary>
		/// Enables the packing if it is not yet enabled.
		/// Use this with the using clause, so at the end the packing is disabled
		/// (and an exception can be thrown if there are errors).
		/// Note: If EnablePacking is nested, only the outer one generates
		/// exceptions. This is on purpose, as small methods may want to pack
		/// some errors, but outer methods may want to pack all the errors of their
		/// inner methods.
		/// </summary>
		public static IDisposable EnablePacking()
		{
			if (_current != null)
				return null;
				
			var result = new _DefaultErrorPack();
			return result;
		}
		
		/// <summary>
		/// Adds an error to the error pack.
		/// </summary>
		public static void Add(object error)
		{
			if (error == null)
				throw new ArgumentNullException("error");
				
			var pack = _current;
			if (pack == null)
				throw new ErrorPackException(error);
				
			pack._actualErrorPack.Add(error);
		}


		/// <summary>
		/// Adds a PropertyError object to the error list.
		/// </summary>
		public static void Add(PropertyInfo property, object error)
		{
			using(new PropertyErrorPack(property))
				Add(error);
		}

		/// <summary>
		/// Adds a PropertyError object to the error list.
		/// Uses an expression to know what propertyInfo to use.
		/// </summary>
		public static void Add<T>(Expression<Func<T>> getPropertyExpression, object error)
		{
			var propertyInfo = ReflectionHelper.GetProperty(getPropertyExpression);
			Add(propertyInfo, error);
		}
		
		/// <summary>
		/// Clears all the errors in the pack and disables the error packing.
		/// It is highly recommended that after dealing with the errors you
		/// call Clear and then dispose the error pack.
		/// </summary>
		public static void Clear()
		{
			var pack = _current;
			if (pack != null)
			{
				pack._baseErrorPack._errors.Clear();
				_current = null;
			}
		}
		
		private static readonly ReadOnlyCollection<object> _emptyErrors = new ReadOnlyCollection<object>(new object[0]);
		/// <summary>
		/// Gets a collection with all the errors.
		/// If there are no errors, an empty collection is returned.
		/// </summary>
		public static ReadOnlyCollection<object> Errors
		{
			get
			{
				var pack = _current;
				if (pack == null)
					return _emptyErrors;
					
				return pack._baseErrorPack._roErrors;
			}
		}
		
		/// <summary>
		/// Gets a value indicating if there are errors packed.
		/// </summary>
		public static bool HasErrors
		{
			get
			{
				var pack = _current;
				if (pack == null)
					return false;
					
				return pack._baseErrorPack._errors.Count > 0;
			}
		}
	}
}

By viewing downloads associated with this article you agree to the Terms of Service and the article's licence.

If a file you wish to view isn't highlighted, and is a text file (not binary), please let us know and we'll add colourisation support for it.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Software Developer (Senior) Microsoft
United States United States
I started to program computers when I was 11 years old, as a hobbyist, programming in AMOS Basic and Blitz Basic for Amiga.
At 12 I had my first try with assembler, but it was too difficult at the time. Then, in the same year, I learned C and, after learning C, I was finally able to learn assembler (for Motorola 680x0).
Not sure, but probably between 12 and 13, I started to learn C++. I always programmed "in an object oriented way", but using function pointers instead of virtual methods.

At 15 I started to learn Pascal at school and to use Delphi. At 16 I started my first internship (using Delphi). At 18 I started to work professionally using C++ and since then I've developed my programming skills as a professional developer in C++ and C#, generally creating libraries that help other developers do their work easier, faster and with less errors.

Want more info or simply want to contact me?
Take a look at: http://paulozemek.azurewebsites.net/
Or e-mail me at: paulozemek@outlook.com

Codeproject MVP 2012, 2015 & 2016
Microsoft MVP 2013-2014 (in October 2014 I started working at Microsoft, so I can't be a Microsoft MVP anymore).

Comments and Discussions