General discussion
-
Topic
-
How do you do n-tier in vb.net
LockedI have a simple question. It concerns how we are suppose to use vb.net
I?m trying to design an equipment hire application.I want to use vb.net to create objects for both the equipment and the maintenance objects. These will be my middle business tier. These objects will talk through ado.net to the database to fill their properties and work any methods.
My first tier will be a windows GUI. It will simply do validation and the textboxes, comboxes etc will be used to set the properties of the EQUIPMENT object that will be instantiated in this assembly.
Here is my problem. All Microsoft examples and those by all the gurus out there link the textboxes and grids etc on a form straight to ado.net. i.e. from 1st tier straight to database. There is no middle business tier. Should the front end change from windows to a web all that code logic is mixed in with the forms. What happened to scalability? What is the point of having vb.net being object oriented if no one uses it the create business objects but links GUI?S straight to a database.
I?m not even sure you can bind a textbox or datagrid to an object you created yourself.
I can?t find any help from Microsoft to help me guide my development process. Is there any one out there who knows what is going on? Is there still a middle business tier in vb.net ?
Josef