After reflecting on the K2 Controls for a couple of minutes it seems apparent that another approach might be preferrable.

We wanted to create a set of generic ASP.NET user controls to solve common lookup requirements (search account, contact etc). In order to easily insert the looked up values from the User Controls into process data we are currently stuffing the values into hidden K2TextBox controls.

Two other options could improve the experience:
1. Be able to subclass a K2UserControl abstract class which exposed an abstract "K2Value" in addition to the designtime support of binding to a process field (just like the K2TextBox).
2. (Preferrable) Have a K2BindingManager which would allow for correlating K2 process fields to any property on any control on the page.

Option 2 would open for design time control of binding K2 process data to any control on the page.

Good idea, or are there any other ways of doing this efficiently with the current version?