Is it possible to create objects at designtime without having to have hard coded class definitions, then populate properties with primitives or even strongly typed data types?

This might sound confusing, so I will attempt to give you a use case scenario.

Use case:

You have an XML config file that could hold configuration values for connecting to various systems in an SOA application. In C# the XML file is read, but for each system the configuration properties are different (e.g: SQL might have a connection string, while SharePoint might need a username + password + domain + url, while yet an smtp server would need username + password + port + url)

So instead of creating static classes as follows

public class SharePointConfiguration or public class SQLConfiguration, then have each class with custom properties (this is cumbersome)

or

using a 1990's method, an arrayList or some named collection

Is there not a more preferred way to achieve this? Taking advantage of new language features, that can still offer design time intellisense, which would make the code easier to maintain and less prone to error.

Thanks