Create objects from a configuration file

Anyone think this is a good idea?
http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedbackid=42c20106-de27-4fb8-88e4-1bf13598c4e1

-Jamie

Hello Jamie,

How far would you go?

If I choose to export a whole package worth of configurations are you saying

that I should be able to take this to a blank package, point it at the config

file and it would at "Just Before Runtime" create everything for me?

You can imagine the hit associated with this, validation would be costly.

What about Connection Managers? sensitive data?

How would you design workflow in a configuration file?

Allan

> Anyone think this is a good idea?

> http://lab.msdn.microsoft.com/ProductFeedback/viewfeedback.aspx?feedba

> ck id=42c20106-de27-4fb8-88e4-1bf13598c4e1

>

> -Jamie

>

|||Nope, I'm not saying that at all. This isn't a runtime thing - just an aid to developer productivity.

e.g. All my packages will be inserting into the same database. I have a configuration set up for a connection manager for that database. Whenever I start to build a new package I can just point at an existing configuration and say "create the object that this configuration references in my current package". Then the developer continues as normal building his/her package with whatever functionality it requires.

-Jamie|||Would this approach be extended to putting standard code for error handling, logging, event handling, etc...?|||

Not really. This is talking about something alot more specific than that.