The release of ASP.NET Core 1.0<\/a> has enticed existing ASP.NET customers to migrate their projects to this new platform. While working with a customer to move their assets to ASP.NET Core, we encountered an obstacle. Our customer had a many configuration files ( The new configuration model<\/a> handles configuration values as a series of name-value pairs. There are built-in configuration providers to parse (XML, JSON, INI) files. It also enables developers to create their own providers<\/a> if the current providers do not suit their needs.<\/p>\n By following the documentation outlined in Writing custom providers<\/a>, we created a class that inherited from *.config<\/code>) they used regularly. They had hundreds of configuration files that would take time to transform into a format that could be consumed by the existing configuration providers. In this post, we’ll show how to tackle this hurdle by utilizing ASP.NET Core’s configuration extensibility model. We will write our own configuration provider to reuse the existing *.config<\/code> files.<\/p>\nCreating the ConfigurationProvider<\/h2>\n
ConfigurationProvider<\/code>. Then, it was a matter of overriding the public override void Load()<\/code> function to parse the data we wanted from the configuration files! Here’s a little snippet of that code below.<\/p>\n