Is it possible to have 3-tier design with BindingContext
-
I try to design an database application with 3 tier,design. So is it possible to pass all the Binding Context from User Interface Layer (UI Layer) to (DATA Layer) and then update the Binding Data in Logic Layer ? Where DATA LAYER is a data class which is collection of the Field Name and Value only. Sorry for my poor english..:sigh:
-
I try to design an database application with 3 tier,design. So is it possible to pass all the Binding Context from User Interface Layer (UI Layer) to (DATA Layer) and then update the Binding Data in Logic Layer ? Where DATA LAYER is a data class which is collection of the Field Name and Value only. Sorry for my poor english..:sigh:
What is a 3 tier,design ? :sigh:
-
What is a 3 tier,design ? :sigh:
Sorry for my poor english to make you confuse.. A typical 3.Tier Architecture is write the software in 3 part. 1.Presentation Tier 2.Bussiness Tier 3.Data Access Tier Please check out link below: http://www.c-sharpcorner.com/Tutorials/Building3TierAppPA.asp[^]
-
Sorry for my poor english to make you confuse.. A typical 3.Tier Architecture is write the software in 3 part. 1.Presentation Tier 2.Bussiness Tier 3.Data Access Tier Please check out link below: http://www.c-sharpcorner.com/Tutorials/Building3TierAppPA.asp[^]
Thanks for da link man:-D,sorry i cant answer your question !:(( Did you check out my question about the "ticket system":-D
-
I try to design an database application with 3 tier,design. So is it possible to pass all the Binding Context from User Interface Layer (UI Layer) to (DATA Layer) and then update the Binding Data in Logic Layer ? Where DATA LAYER is a data class which is collection of the Field Name and Value only. Sorry for my poor english..:sigh:
kakarato wrote: Where DATA LAYER is a data class which is collection of the Field Name and Value only. Yes. However, in your data class you'll need to implement properties for your fields. You class needs to implement [propertyName]Changed events for all your properties, and the property setters need to check if the value has changed and, if the xxxChanged event is not null, fire the event. Also, you need to initialize your fields usually. If you don't do the event stuff, you won't get 2 way data binding. Like this:
public class MyData { protected string myText; public event EventHandler MyTextChanged; public string MyText { get {return myText;} set { myText=value; if (MyTextChanged != null) { MyTextChanged(this, EventArgs.Empty); } } } public MyData() { myText="Initial Value"; } }
I was going to write an article on "Intro to data binding" at some point! Marc My website
Latest Articles: Undo/Redo Buffer Memento Design Pattern -
kakarato wrote: Where DATA LAYER is a data class which is collection of the Field Name and Value only. Yes. However, in your data class you'll need to implement properties for your fields. You class needs to implement [propertyName]Changed events for all your properties, and the property setters need to check if the value has changed and, if the xxxChanged event is not null, fire the event. Also, you need to initialize your fields usually. If you don't do the event stuff, you won't get 2 way data binding. Like this:
public class MyData { protected string myText; public event EventHandler MyTextChanged; public string MyText { get {return myText;} set { myText=value; if (MyTextChanged != null) { MyTextChanged(this, EventArgs.Empty); } } } public MyData() { myText="Initial Value"; } }
I was going to write an article on "Intro to data binding" at some point! Marc My website
Latest Articles: Undo/Redo Buffer Memento Design Pattern