ADO.Net Activity Pack Designers Must Support Connection Strings from Variables/Arguments

Mar 20, 2012 at 9:55 PM
Edited Mar 20, 2012 at 9:56 PM

Hey guys I cannot believe that somehow you thought that the only way in which a connection string value would be set is in the configuration file or in the WF itself hardcoded. We MUST get designer support for binding this to an Argument<T> or Variable<T> on the workflow ASAP. This makes this activity library only useful for the most limited of scenarios.

Right now I have to resort to building this in code and that's not fun.