«

Hi,
i was in the book store this weekend checkingout some ASP.NET books. I
noticed that many do not use the "new" code-behind model much. Why is
this?

What do you ASP.NET developers use and why?

thanks much.

To code behind or not, it is the same when it comes to performance.
But I think most of web developers prefer to use code behind, because they'd
like to separate code from presentation, so designers can work with aspx and
code developers work with vb or cs.
Also this made your project much easier to navigate and work with.
Books my refere to inline coding just for simplification, and in later
chapters they should mention the code behind technique..
any way, this is only reflect my idea and opinion
Regards,
--
Muhammad Mosa
Software Engineer & Solution Developer
MCT/MCSD.NET
MCTS: .Net 2.0 Web Applications
MCTS: .Net 2.0 Windows Applications


"farseer" wrote:

> Hi,
> i was in the book store this weekend checkingout some ASP.NET books. I
> noticed that many do not use the "new" code-behind model much. Why is
> this?
>
> What do you ASP.NET developers use and why?
>
> thanks much.
>
>

Based on my own experience, if I want a single - file page that is easy to
show as an example, that is usually when I use inline server-side <script>.
So it makes sense possibly for a book, and also because in the early days of
..NET the original ASP.NET developers came from the classic ASP space where
there is no such thing as "Codebehind". In fact, the original IBuySpy
reference app was written in all inline code with no codebehind files.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com




"farseer" wrote:

> Hi,
> i was in the book store this weekend checkingout some ASP.NET books. I
> noticed that many do not use the "new" code-behind model much. Why is
> this?
>
> What do you ASP.NET developers use and why?
>
> thanks much.
>
>

i am all of the separation of code from presentation...my biggest gripe

however is that it's not like the old days when you can make changes on

the fly if needed. Now, for any change that you need to make, you must

recompile the distributable dll and re-publish your web-site. That to
me is a bit discouraging as compared to code that is actually embedded
in a single file and compiled ont he fly (like JIT).


Peter wrote:
> Based on my own experience, if I want a single - file page that is easy to
> show as an example, that is usually when I use inline server-side <script>.
> So it makes sense possibly for a book, and also because in the early days of
> .NET the original ASP.NET developers came from the classic ASP space where
> there is no such thing as "Codebehind". In fact, the original IBuySpy
> reference app was written in all inline code with no codebehind files.
> Peter
>
> --
> Co-founder, Eggheadcafe.com developer portal:
> http://www.eggheadcafe.com
> UnBlog:
> http://petesbloggerama.blogspot.com
>
>
>
>
> "farseer" wrote:
>
> > Hi,
> > i was in the book store this weekend checkingout some ASP.NET books. I
> > noticed that many do not use the "new" code-behind model much. Why is
> > this?
> >
> > What do you ASP.NET developers use and why?
> >
> > thanks much.
> >
> >

"farseer" <> wrote in message
news: oups.com...

>i am all of the separation of code from presentation...my biggest gripe
> however is that it's not like the old days when you can make changes on
> the fly if needed. Now, for any change that you need to make, you must
> recompile the distributable dll and re-publish your web-site. That to
> me is a bit discouraging as compared to code that is actually embedded
> in a single file and compiled ont he fly (like JIT).

You can't possibly be serious...???

This isn't a valid comparison. The "old days" (classic asp) was interpreted
code. This is compiled code. My suggestion: "get over it!".
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com




"farseer" wrote:

> i am all of the separation of code from presentation...my biggest gripe
>
> however is that it's not like the old days when you can make changes on
>
> the fly if needed. Now, for any change that you need to make, you must
>
> recompile the distributable dll and re-publish your web-site. That to
> me is a bit discouraging as compared to code that is actually embedded
> in a single file and compiled ont he fly (like JIT).
>
>
> Peter wrote:
> > Based on my own experience, if I want a single - file page that is easy to
> > show as an example, that is usually when I use inline server-side <script>.
> > So it makes sense possibly for a book, and also because in the early days of
> > .NET the original ASP.NET developers came from the classic ASP space where
> > there is no such thing as "Codebehind". In fact, the original IBuySpy
> > reference app was written in all inline code with no codebehind files.
> > Peter
> >
> > --
> > Co-founder, Eggheadcafe.com developer portal:
> > http://www.eggheadcafe.com
> > UnBlog:
> > http://petesbloggerama.blogspot.com
> >
> >
> >
> >
> > "farseer" wrote:
> >
> > > Hi,
> > > i was in the book store this weekend checkingout some ASP.NET books. I
> > > noticed that many do not use the "new" code-behind model much. Why is
> > > this?
> > >
> > > What do you ASP.NET developers use and why?
> > >
> > > thanks much.
> > >
> > >
>
>

i think you are correct muhammed, anyway i wanted to ask you where to
take the MCTS course in egypt, thnx

Sharing makes All the Difference

--
Sent via .NET Newsgroups
http://www.dotnetnewsgroups.com