Todd,
With the power of ASP.NET, I would place the bulk of my code in ASP.NET. I
would use stored procedures on SQL Server, largely handling CRUD (Create,
Retrieve, Update, Delete). I would resort to a trigger only if there was an
interface to the data that did not allow the use of stored procedures.
I would only get an "application server" involved, if I really need one. If
I used an "application server" I would favor .NET Remoting over Web Services
for communication, as I find Web Services are more for external interfaces
to your app, not internal interfaces between layers.
Of course my ASP.NET code would be fully OOP.
Hope this helps
Jay
"Todd" <tm*******@yahoo.com> wrote in message
news:00****************************@phx.gbl...
Where do I place my code? I am learning VS.NET 2003 but
have a big picture question on how to build applications.
The way I see it, I have three places I can place code. I
can place code on the webserver (front end), the
application sever(s), and the back-end SQL Server. It
seems to me, the best practice is to place as much code on
the SQL Server (called through triggers) and on the
middle "application server" and as little as possible on
the web server. Is this correct? I have been studying many
ASP.NET and VB.NET books, and it seems no one addresses
this design topic clearly.