Although I am avidly reading the manual, I need to employ UserControls. I am building a WinForms application whose driving force is the navigation of Construction Projects. These projects have a large number of aspects to deal with that can be best (IMHO) handled by a TreeView leading to 'presentations' that very often posses multiple aspects which lend themselves to tabpage format. I say 'presentations' because one could use forms but for re-usability (even considering base forms) I've found that UserControls better suit the purpose - and that means UserControls within UserControls. Last month a thread by Duncan McDonald ran on just this subject.

What I have encountered is that I (having come from the DataSet world) have added my BizObjs - generated nicely by the BLG - to the solution's DataSources. When I place a control on my UserControl - say, mmTextBox - and attempt to set the 'BindingSource' property, nothing appears in the dialog. I imagine that is because my BizObjs of interest are not registered with that UserControl. If I use a non-mm control, setting the "DataSource' property causes Visual Studio to generate a BindingSource for my BizObj and place it in the non-visual designer tray. The BindingSource+BizObj combination, while permitting display of the bound data, does not seem to communicate regarding modifications to that data!

So, then, what should the correct approach to utilizing UserControls be, while sticking strictly to BizObjs ???