So I understand that there is no dropping of BO's on webforms, you create the BO reference in your ApplicationBasePage and it available to the entire website. Check.



Does that mean I need to create many BO's if I need them populated differently? For instance I have a BO that contains codes used to fill all my applications dropdowns, I have a BO on each form that calls a fill specific for the proper contents of the BO based on a "codetype" field.



So the generic question is this, since BO's essentially don't get instantiated into individual objects on a webform where I can call different fill methods, is the answer to make many BO's specified to their task, or am I on the wrong path?

Keith Chisarik

Well, you are embarking upon the quest that we have battled from the beginning...Microsoft's inconsistent controls.   Just do this, drop on a text box and play with the properties (Backcolor, ForeColor, etc) until you get the look you are going for.  Once this is done, just create your own textbox that inherits directly from the .NET control (not ours).  Then open up the SF source code, and look at the Web TextBox control.  Copy all of the guts out of this thing...in fact, you can copy this whole class and just rename the class to your new class...obviously in a different project than the SF source.

There is an interface property called BindingEditable.  The code inside of here is what managed the readonly state.  You will see that the code currently controls the Enabled property.  Place your code here...just keep in mind that the standard .NET control does not let you control the disabled background and foreground colors..thus the problem we have dealt with.  It basically will require us doing some rendering, which we just hve not taken the time to do, when the control is disabled.