General discussion


What's your ASP.NET coding strategy?

By MaryWeilage Editor ·
In this week's .NET e-newsletter, columnist Tony Patton discusses choosing your ASP.NET coding strategy. The discussion of inline and codebehind code has been raging since the introduction of ASP.NET. Let us know your thoughts on this topic.

If you aren't subscribed to the .NET TechMail, visit our e-newsletter subcenter to subscribe to this free e-newsletter:;tag=fb

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

ASP coding strategy

by vman_prog In reply to What's your ASP.NET codin ...


Placing javascript to injecting Client-Side Script from an ASP.NET Server Control to fullfill the requirements below, is spaghetti code and I should only use .NET to fullfill these requirements? What about performance?

1) two list box
2) ability to load list box on the right with values from xml file or database
3) move unique values selected one or more from right listbox to left listbox
4) remove unique values selected one or more from left listbox back to right listbox
5) exit button to exit
6) cancel button to not save
7) ok button to save values in left listbox to xml or database

Collapse -

ASP coding strategy

by vman_prog In reply to ASP coding strategy

I feel that javascripting is the way to go with these situations because of all the processing need to accomplish i.e. user experience look and feel of a windows client/server application on the Web.

I'm I wrong?

Collapse -

ironic choice of words

by ay_ca In reply to What's your ASP.NET codin ...

".....when lamenting the merits of .NET"

"Lamenting"? Was this really the word intended? It certainly changes how I read that paragraph!

Collapse -

RE: Ironic choice of words

by Bad Boys Drive Audi In reply to ironic choice of words

I wondered the same when I read that sentence. I'm pretty sure that he didn't quite re-read his article.

Collapse -

Radical Scripter turns himself in...

by activemode In reply to What's your ASP.NET codin ...

I was once one of those people who thought that scripting was all that I would ever need in this life. Not only was I able to mix html, asp and javascript on the same page, I based an entire website on that philosophy... then came .NET

It took 6 months to script. And now I've working on the .NET revisions for over a year and a half.

My strategy is simple. Study the blasted programming language and design properly, or suffer further aggrivation.

I prefer to have the code in the head of the page, so that I can see it. I use Codebehind only in the sensitive areas where code is redundant, and re-used.

Collapse -

Some things never change...

by Meisinger In reply to What's your ASP.NET codin ...

I remember this debate when ASP was the next best thing since slice bread. COM developers would load up the middle layer with DLL files that were larger than you can imagine. ASP developers would copy and paste the same code over and over again making it easier to rewrite the whole application rather than updating the ASP code.

Either way you looked at it... It sucked!

It all comes down to middle ground on this topic. You will have times when there needs to be VB.Net or C# code written in-line. More times than not, however, you will have most of the code in code-behind files.

I think that we should take a page out of the JSP book on this topic. I don't think I have ever seen on JSP project where this came up. Now that I think about it, I don't think I have ever seen a "heavy" JSP page.

Collapse -

Started this "code behind" strategy with Zope

by Bad Boys Drive Audi In reply to Some things never change. ...

After I was introduced to Zope, and its mark-up (DTML), I quickly became fustrated with regular ASP. I think that I'll have an easier time with code-behinds based on the little time that I spent with Zope.

However, there are always going to be times when you'll need to embed some code within the design file. Guaranteed.

It's just nice that I now have a choice, and can follow what strategy makes the most sense for the project.

Collapse -

Al very well

by maartin In reply to What's your ASP.NET codin ...

This is all very well in broadband scenarios but now what about the very limited band scenarios?

Then you have to minimize the server postbacks and that is where javascript rules. Take that from somebody who is not a javascript fan and who realy loves the oop approach.

This seems to be an issue which MS and a lot of other people forget. We are curently developing a system for election results and we can not have mullions of calls to the server for data etc. We employ caching etc but still you can not live for server side code only.

Even MS has started to realize this as MS CRM utilizes javascript as well.

Well those where my thoughts.

Related Discussions

Related Forums