R
Roy
Recently I've been trying to convert over my sqldatasource's to
objectdatasource's to take advantage of the custom paging functionality
of objectdatasource's. These attempts have plunged me knee-deep into
unfamiliar territory and I'm starting to feel like a rank newbie. What
makes it worse is that---despite my best efforts---I'm struggling to
get anywhere. There's just a lot of theory here I don't understand.
1.) I understand (I think) the core concepts of Business Logic Layers
and Data Access Layers. They are a middle tier between the web front
end and the database back end. But how are they different? They sound
like different names for the same thing.
2.) The examples I've found online of BLL's and DAL's show some
connection strings written in VB or C#. Ok. So BLL's and DAL's are just
functions written in VB or C# that connect to a database. How is this
any different from simply writing the same code in the page's
codebehind? What's the point of creating yet another VB file?
3.) Why are they stored in the app_code directory? Is this just simple
organization or is there some compiling thing going on here that I
don't get?
4.) This may be answered by question 2, but what's the advantage of
creating a BLL/DAL? It must be a pretty big advantage since they figure
so prominently in the world of the objectdatasource, but to my eyes it
just looks like something that would slow down the whole web experience
for a user.
As you can see, I'm quite confused. Can someone shed some light for me?
Thanks much!
objectdatasource's to take advantage of the custom paging functionality
of objectdatasource's. These attempts have plunged me knee-deep into
unfamiliar territory and I'm starting to feel like a rank newbie. What
makes it worse is that---despite my best efforts---I'm struggling to
get anywhere. There's just a lot of theory here I don't understand.
1.) I understand (I think) the core concepts of Business Logic Layers
and Data Access Layers. They are a middle tier between the web front
end and the database back end. But how are they different? They sound
like different names for the same thing.
2.) The examples I've found online of BLL's and DAL's show some
connection strings written in VB or C#. Ok. So BLL's and DAL's are just
functions written in VB or C# that connect to a database. How is this
any different from simply writing the same code in the page's
codebehind? What's the point of creating yet another VB file?
3.) Why are they stored in the app_code directory? Is this just simple
organization or is there some compiling thing going on here that I
don't get?
4.) This may be answered by question 2, but what's the advantage of
creating a BLL/DAL? It must be a pretty big advantage since they figure
so prominently in the world of the objectdatasource, but to my eyes it
just looks like something that would slow down the whole web experience
for a user.
As you can see, I'm quite confused. Can someone shed some light for me?
Thanks much!