Exporting to MS Excel is a common feature for data driven business apps. And it is very common that an individual app contains several such export features that take different data respect to different needs and export to Excel. The purpose this blog post is to provide a generic solution using .NET Reflation and Generics so the same export function can be reused through the entire application regardless of the object type and save us a lot of effort.
Engineers spend several hours to write redundant function contains such export features satisfy different needs. with a little twist codes can be reused. But question is why is we implement different function for same purpose answer is simple each object has different property so excel will contains different column name for each object. So programmers write different export functions that address a specific object type and hard coded the excel column name .
How Reflection can Help
To address this issue we can use .net Generics and Reflection. Lets not stretch the post by introducing them, you will find lots of good post about them, if you just google. Our interest is on a particular feature reflection can do, you will see PropertyInfo.
Use PropertyInfo to discover information such as the name, data type, declaring type, reflected type, and read-only or writable status of a property, and to get or set property values.
So idea is we will use a Generic collection to export and use Reflection to iterate all property via PropertyInfo, thus we can get all property name/type all that whatever the object collection is provided. Once we have property name/ type we can do whatever data formatting or processing we need according to our needs. Say for a particular app specification is whatever date time is exports to excel it should contains only time expressed in terms if milliseconds. As we have property type now , we can do that easily right?
Here is the method that take Generic List<t> as parameter and use reflection to iterate the type and export accordingly.
public static void ExportListToExcel<T>(List<T> listToExport, string xlsName)
"attachment; filename=" + xlsName + ".xls");
Int32 success = 0;
string sep = "";
PropertyInfo fieldInfo = listToExport.GetType().GetProperties();
foreach (PropertyInfo col in fieldInfo)
if (col.PropertyType != typeof(EntityKey) && col.PropertyType != typeof(EntityState))
HttpContext.Current.Response.Write(sep + col.Name);
sep = "\t";
foreach (T dataItem in listToExport)
PropertyInfo allProperties = dataItem.GetType().GetProperties();
sep = "";
foreach (PropertyInfo thisProperty in allProperties)
if (thisProperty.PropertyType != typeof(EntityKey)
&& thisProperty.PropertyType != typeof(EntityKey))
object value = thisProperty.GetValue(dataItem, null);
String propetyValue = (value == null ? String.Empty : value.ToString());
HttpContext.Current.Response.Write(sep + propetyValue.ToString());
sep = "\t";
catch (Exception ex)
One thing might you notice above
if (thisProperty.PropertyType != typeof(EntityKey) && thisProperty.PropertyType != typeof(EntityKey))
Why we need this checking? you see if you are using Entity Framework in your app, all entity has these two additional property type predefined and we don’t what them to be exported to csv and confuse end user, do we? So additional checking is required to remove them. If you do not use Entity Framework you don’t need to worry about this checking.
So you can see a simple trick can save lots of development effort, enjoy the free time