Think you have a .Net application using a custom config section on its config file. As the application evolves, config sections also evolve too. You distribute your application to several customers. For example, one old application uses a config file with new config section by mistake. But the application works without crash because new config file does not cause braking changes. But you have to inform the user that the config file the application used is newer than expected. How can you apply a versioning strategy to solve this problem or anything other than versioning?Think you have a .Net application using a custo