Re: ASP vs ASP.NET
From: WebMatrix (WebMatrix_at_discussions.microsoft.com)
Date: 11/20/04
- Next message: Laura K: "Re: ASP vs ASP.NET"
- Previous message: Bob Barrows [MVP]: "Re: Problems in open new browser"
- In reply to: Nathan Sokalski: "Re: ASP vs ASP.NET"
- Next in thread: Paxton: "Re: ASP vs ASP.NET"
- Reply: Paxton: "Re: ASP vs ASP.NET"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 20 Nov 2004 08:43:08 -0800
Nathan,
I think before reading that article, you should read up more on the basic
concepts of web / browsers technology.
Why would you expect to see anything other than standart HTML if you "view
source". It doesn't matter what generated that page ASP, ASP.NET, PHP,
ColdFusion whatever, browser can only understand HTML. And why would it
matter if MS would 'convert' their site to XML, they might be running XML on
the back-end anyway for all we know, but again at some point it has to be
converted to HTML, that's all that browsers can understand.
As far as your ASP vs. ASP.NET concerns... again all ASP.NET elements either
server control tags or server control objects in the code will be rendered as
HTML eventually. You can still have static HTML in your page, just embed
server side controls where dynamic elements should go. But the advantages of
that are enormous; you have so much programming control over a web page and
its elements.
If you were asked to develop a page that displays over thousands records,
users want to be able to page through records, say 20 rec per page, and also
they want to be able to sort by columns asc/desc. How long would it take you
to develop something like that in ASP? How many lines of code would it take?
Well, in ASP.NET I could put together a page like that in 20-30 min without a
lot of coding. Taking a coffee break in between.
"Nathan Sokalski" wrote:
> I am not agreeing or disagreeing with anything you said about Microsoft,
> because that has almost nothing to do with my question. My question was
> asking what other people's opinions were as to their preferences and
> advantages/disadvantages between ASP and ASP.NET were. I will let you know,
> however, that I think Microsoft's website is one of the most poorly designed
> sites I have ever seen, and many of my friends agree. Maybe if we get lucky
> they will improve it if they ever decide to convert it to XML, since they
> have been doing a lot of work on XML technologies (although I'm not going to
> get my hopes up!).
> --
> Nathan Sokalski
> njsokalski@hotmail.com
> www.nathansokalski.com
>
> "Jim Carlock" <anonymous@127.0.0.1> wrote in message
> news:OKHnQ%23qzEHA.2600@TK2MSFTNGP09.phx.gbl...
> > I'll give a counterpoint.
> >
> > 1) Take a look at the speed on Microsoft's own website.
> > 2) Take a look at the broken links, missing pages, and the
> > common mis-use of redirection.
> > 3) Microsoft ABUSES redirection.
> > 4) In all their abuse of redirection, they still have broken links.
> >
> > Realize these points...
> >
> > 1) Microsoft HAS the FASTEST computers in the world.
> > 2) Microsoft HAS the FASTEST networks in the world.
> > 3) Microsoft EMPLOYS the most SKILLED people in the world.
> > 4) Microsoft BUILT the webservers they use.
> > 5) There is NO EXCUSE at Microsoft (they have alot of problems).
> >
> > AND WITH everything they know, ask yourself if www.microsoft.com
> > runs as fast as it could. And if it doesn't run as fast as a webpage
> > should, what is the biggest limiting factor? Could the Microsoft
> > employees do a better job with php or coldfusion or even with
> > ASP.Net ?
> >
> > --
> > Jim Carlock
> > Post replies to newsgroup.
> >
> > "Nathan Sokalski" <njsokalski@hotmail.com> wrote in message
> > news:%23iMXC%23pzEHA.1308@TK2MSFTNGP09.phx.gbl...
> > 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
> >
> >
> >
>
>
>
- Next message: Laura K: "Re: ASP vs ASP.NET"
- Previous message: Bob Barrows [MVP]: "Re: Problems in open new browser"
- In reply to: Nathan Sokalski: "Re: ASP vs ASP.NET"
- Next in thread: Paxton: "Re: ASP vs ASP.NET"
- Reply: Paxton: "Re: ASP vs ASP.NET"
- Messages sorted by: [ date ] [ thread ]