Code-Behine VS inline-Coding

[Reza Alirezaei]

when we should use Code-Behine and when inline-Coding??? which one is better
and why???

thanks for your time

[Marina]

Code behind is always better as far as maintainability, extensibility, and
object orientation goes. So it is always the better way to go as far as good
coding practices. Inline coding is often faster - but to get away from the
ASP mindset I would recommend staying away from that.

"Reza Alirezaei" <an*******@discussions.microsoft.com> wrote in message
news:OM**************@tk2msftngp13.phx.gbl...

when we should use Code-Behine and when inline-Coding??? which one is better and why???

thanks for your time

[Flare]

> Code behind is always better as far as maintainability, extensibility, and

object orientation goes. So it is always the better way to go as far as good coding practices. Inline coding is often faster - but to get away from the
ASP mindset I would recommend staying away from that.

I dont agree with that. Yes codebehind DOES provide better maintainability
and extensibility. But thats for Buissness like code. Not hiding simple
controls and in general manipulating the webcontrols. It ugly and dont fit
well with maintainability, extensibility. I seen too many cluttered ....1000
lines classes with maybe 150 line of real logic.

One big problem was (is) that Visual Studio 2003 doesent support
code-completion in inline code. That will change in VS 2005. Here we are
actually encuraged to write such GUI code inline where it belongs. Then you
implement the rest of the logic in the codebehind. This is even an elegant
way of doing it with the intruduction of partial classes (units of the same
class is defined in serval files/chunks)

But of course. Everything can be discussed.

Anders K. Jacobsen, Denmark