RE: ASP vs ASP.NET

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Michael Geist (Geist_at_discussions.microsoft.com)
Date: 11/23/04 

Date: Tue, 23 Nov 2004 12:27:03 -0800

I am struggling with the same question but perhaps for different reasons. I
have been building web applications for about 7 years with (mostly) script
and some COM. I am comfortable with OOP and have taken several
Microsoft-designed ASP.NET courses including their ASP to ASP.NET course
(which in my opinion is a waste of time for anyone with more that a passing
familiarity with ASP) and the ASP.NET Bootcamp (more useful but still didn't
solve my problem). Not to sound discouraging, but I am not sure that
appreciating how and why ASP.NET works will resolve your dilema.
Most of my development is Intranet (IE 5.5+) based and, admittedly, I
frequently build funtionality with ASP that is more appropriate in COM or
ASP.NET but my issue is that I now have a great deal of reusable code
(infrastructure, if you will) and complex techniques that allow me to be VERY
productive with ASP. ASP.NET promises great reduction in development time
but for me it may mean months of a gnificantly longer development cycles
because I hardly know how to begin to create in .NET the pages and modules
that are second nature to me in classic.
Transitioning content and code from ASP to ASP.NET is one thing but does
anyone have suggestions for speeding the transition of skill and productivity?

Michael Geist
MCSD (6)

"Nathan Sokalski" wrote:

> I was recently looking at a page about transitioning from ASP 3.0 to
> ASP.NET. (The page I was looking at is located at
> http://www.4guysfromrolla.com/webtech/041601-1.shtml ). It looks to me like
> they are taking away what has always seemed to me like the beauty of ASP. I
> always viewed the beauty of ASP as giving you the ability to fill in the
> dynamic areas without the need to change your HTML layout techniques. But
> ASP.NET seems to be trying to make you replace all HTML elements with
> ASP.NET code. For example, on the page I mentioned, notice how ASP.NET code
> is used to create the submit button even though the submit button does not
> have any dynamic areas. Also, when initially designing a page, I have always
> preferred to create it with HTML to make it look the way I want and then
> replace the dynamic areas with ASP. And just out of curiosity, for anyone
> who might know, will the "View Source" look the same? Because this is one of
> the primary tools to make sure the code is producing what I want, I need
> this to look the same as it would using ASP. Does anyone else have an
> opinion on whether ASP.NET is really better? Even though I have not yet
> learned much about coding in ASP.NET, what I have seen makes me lean towards
> ASP 3.0.
> --
> Nathan Sokalski
> njsokalski@hotmail.com
> www.nathansokalski.com
>
>
>

Quantcast