ASPX or ASP.Net (Full Version)

All Forums >> [Web Development] >> ASP, PHP, and Database



Message


Ziggyzaz -> ASPX or ASP.Net (12/4/2003 19:54:02)

I was just wondering what people have heard of this and what they think of it and really what it is. Any information would be helpful and I appreciate all of it. Thanks in advance




Doug G -> RE: ASPX or ASP.Net (12/5/2003 0:22:21)

www.microsoft.com
http://www.asp.net/Default.aspx?tabindex=0&tabid=1




rdouglass -> RE: ASPX or ASP.Net (12/5/2003 9:36:54)

I don't think it's an "either / or" situation. My understanding of it is that for an .aspx page to run, it needs the .NET components installed on the server/host. That's what the "x" part of it signifies.

I am in the process of converting some of my sites to .NET but I still don't see any big advantages of the Data Grid over writing ASP. The Data Grid components seem to have the typical Microsoft "code bloat" (think grey DRW code) and I can do most things with fewer lines of ASP code.

I still haven't got most of my <runat server=""> code stuff working right. IMO, there's a significant learning curve; but I'm trying anyways.

To .NET's benefit, I do see significant performance benefits at the server end. I use a lot of SSI's and the server caches them quite nicely. In fact, most all of my ASP code runs faster (all other things being equal) on IIS 6 (with .NET enabled).

Hey, if we want to dev on MS products, its a matter of "when" and not "if" we move to .NET technologies so I'm trying to use it anyways...




paulie -> RE: ASPX or ASP.Net (12/5/2003 12:32:09)

quote:

Hey, if we want to dev on MS products, its a matter of "when" and not "if" we move to .NET technologies so I'm trying to use it anyways...

I agree with that sentiment, and started investigating .NET with that same attitude several months ago, but the more I learned about it, the more stressed-out I became. It seems to assume that you're from an applications development background, with experience in client-server object-oriented programming. I don't really want to become a "programmer" - I used to write Cobol on the mainframe. I later became certified as a net admin and started working with websites/servers. When I learned ASP, I was delighted to see that you can do just about anything the client wants from a web page with server-side scripting.
To learn everything I need to know to "take advantage of" the benefits of ASP.NET, it looks like I would have to start at square one (again) and become an OO application developer. I'm sure that "Classic ASP" won't be around forever, but as someone else here pointed out awhile back, there's an awful lot of it in production out there. For the time being, it suits my needs quite well.

<edit>
I just want to add that I'm interested in hearing more about how easy the migration is for others. I played with the Web Matrix, bought a couple of books, and coded several pages on a test server. Still seemed like a lot of pain for little gain, but back to Roger's point, I'm sure it's inevitable. Maybe I'll be subcontracting that part of my business by then...[8|]</edit>




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
7.763672E-02