Hi,
I have got a web blog application
the person who has designed it has put all the code in app_code vb classes
how is that? he has ot used codebehind he has just referenced from the pages to the classes like this: inherits="myNamespace.blog"
what is the advantage?is it more professional?
is the any good article about this object oriented programming
here is some sample code:
Namespace myNamespace


    Public Class Blog
        Inherits System.Web.UI.UserControl
        <System.Diagnostics.DebuggerStepThrough()> Private Sub InitializeComponent()

        End Sub
        Private designerPlaceholderDeclaration As System.Object
        Protected WithEvents LblMember As System.Web.UI.WebControls.Label

        Private Sub Page_Init(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Init
            'CODEGEN: This method call is required by the Web Form Designer
            'Do not modify it using the code editor.
            InitializeComponent()
        End Sub

        Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load

            If Not Page.IsPostBack Then
                LblMember.text = "title"


            End If
        End Sub


    End Class

End Namespace

Is there an advantage to using what? Code Behind files vs Not using them or the advantage to using class files?

Personally, I prefer using Code Behind Files because of the seperation of UI and Logic although I do not know of any ups or downs of one method over another. (If there are advanatages and disadvantages id love to hear them)

In so far as Class files are concerned, that is a professional way of doing things. By and large my app_code directory can be broken down into 2 main categories:

DataAccess Layer
Objects

By and large all of the class files associated with my Data Access layer do just that: Access Data. The objects can be any code that I plan to reuse time and time again through out my project. A simple google search on OOP Principals should net you lots of good reads.

================================================== =========
Read this if you want to know how to get a correct reply for your question:
http://www.catb.org/~esr/faqs/smart-questions.html
================================================== =========
Technical Editor for:
Professional Search Engine Optimization with ASP.NET

Professional IIS 7 and ASP.NET Integrated Programming

================================================== =========

Hi keyvanjan,

I just wanted to add that it might be worth keeping in mind that code behind files ARE class files, or to be more exact, partial classes. You will notice they all by default inherit from System.Web.UI.Page.

Also, I recently saw an application recently that took this approach as well, with every "code behind" actually in the App_Code directory. My only thought is that to some people this seems like a better way to organize their classes. It's entirely preferential though. Neither way is more "professional" in my opinion.