ASP.NET vs ASP

  • Thread starter Thread starter shank
  • Start date Start date
S

shank

Questions for programmers that have migrated from ASP to ASP.NET....

Are you happy you've made the commitment to migrate? Did you happen to
migrate for a specific reason? Did you migrate just because it's the newest
toy in town? Was it a steep learning curve? Has anyone tried it and gone
back to ASP?

I feel that I should learn something other than ASP just to keep the mind
working. I've been told that PHP and MySQL is pretty cool to work with. But
I'm figuring that if I decide to learn something, maybe it should be
ASP.NET. Can I get a few opinons?

thanks!
 
If you've got experience in ASP and VB then it's easy.
No-one would go back to ASP. You'll understand what I mean once you get
going.
Get a good book on APS.NET , read it from cover to cover, then do some
practice forms and then read the more advanced sections again.
Also , check out www.aps.net
If you don't have VS.NET, download Web Matrix from www.asp.net.
Instructions for installing MSDE are also on www.asp.net

Don't waste your time with PHP. It's a kiddies toy compared to ASP.NET.
MySQL is ok but MSDE is easier to get going with .
Andrew
 
shank said:
Questions for programmers that have migrated from ASP to ASP.NET....

Are you happy you've made the commitment to migrate? Did you happen to
migrate for a specific reason? Did you migrate just because it's the newest
toy in town? Was it a steep learning curve? Has anyone tried it and gone
back to ASP?

ASP.Net represents a sea change in how web applications are developed,
bringing them more in line with the form, code/interface separation, and
event model that most application development is done with. This was one of
the easiest decisions we had to make when the .NET fork in the road came
along - we adapted it for all our new work. (Porting old asp has been
hellish, but there is a new tool on www.asp.net that does an alright job.)

We migrated because moving to a more 'normal' style of development allowed
us to split up UI design from coding. The performance improvements are
incredible, the structured error handling a godsend (asp provided this in
limited measure, but only if you used jscript.) And the ability to use
classes and object oriented techniques enabled us broadly to make extensive
use of all our existing patterns and methods, without resorting to
copy/paste to get them in there!
I feel that I should learn something other than ASP just to keep the mind
working. I've been told that PHP and MySQL is pretty cool to work with. But
I'm figuring that if I decide to learn something, maybe it should be
ASP.NET. Can I get a few opinons?

I use MySQL at home, with ASP. I haven't done much PHP, but it certainly has
advantages over ASP. But it isn't as close to "real programming" as ASP.Net
is. ASP.net skills are transferable to desktop applications, and device
applications.

R.
 
shank said:
Questions for programmers that have migrated from ASP to ASP.NET....

Are you happy you've made the commitment to migrate?
Absolutely!

Did you happen to migrate for a specific reason? Did you migrate just because it's the newest
toy in town?

I own a technology training company and so, I must stay current on what's
out there. I actually started working with ASP.NET in its earliest beta
form, back when it was going to be called ASP+.
Was it a steep learning curve? Has anyone tried it and gone back to ASP?

Steep? Well, not steep, but ASP and ASP.NET are completely different
architectures that use different programming languages, so you need to get
up to speed on the .NET language and understand the architecture. I can't
imagine writting "Classic ASP" pages at this point. Sure, there are still
millions of "Classic ASP" pages out there that will need to be maintained if
they are not going to be mirgrated, so "Classic ASP" will still be with us
for some time, but for new applications, no question about it, ASP.NET is
the way to go.
I feel that I should learn something other than ASP just to keep the mind
working. I've been told that PHP and MySQL is pretty cool to work with. But
I'm figuring that if I decide to learn something, maybe it should be
ASP.NET. Can I get a few opinons?

..NET is not a fad, it's a proven technology that represents a paradigm shift
in Windows development. If there will be any Windows development in your
future, then better to learn .NET now.
 
Are you happy you've made the commitment to migrate? Did you happen to
migrate for a specific reason? Did you migrate just because it's the newest
toy in town? Was it a steep learning curve? Has anyone tried it and gone
back to ASP?

The biggest reason to learn and use ASP.Net over ASP is simply programming
power. ASP.Net is extremely powerful, and can do so much more than ASP that
it's not possible to quantify the difference. As for the learning curve,
well, think of ASP as a Cessna. Think of ASP.Net as a Boeing 747. Which one
is easier to fly? Which one can do more?

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
http://www.takempis.com
Big Things are made up of
Lots of Little Things.
 
While both ASP and ASP.NET have
"ASP" in their names, they are very different. Just like C# and C++ sound the
same but are completely different languages and VB6 and VB.NET have similar
sounding names but are completely different languages.

ASP.NET is complete paradigm shift from the methodology and model of legacy
environments such as ASP. PHP and CGI.

ASP.NET is part of the .NET family of technologies. As such, it uses the over
3,400 framework classes that are available to anyone developing apps with .NET.
The code and presentation are completely separated (altho, someone who
develops using Notepad as opposed to one of the IDE's, may end up mixing the
code and the html onto the same page, the way old fashioned web development
used to be back in the ASP and CGI days -- this is not a good practice).

Programming is done with completely object oriented languages such as VB.NET
and C#. You can also use COBOL.NET, Perl.NET, J#.NET and managed C++. But
most people will be using VB.NET/C# (these two languages are so similar that
people routinely switch from one to another). If you plan to do ASP.NET
development, you must learn one of these languages. Keep in mind that while
VB.NET and C# are very, very similar (almost to the extent of being variations
of the same language), VB6 and VB.NET are not that similar and C++ (or Java)
and C#, while similar, are not the same language. However, if you know Java or
C++ it is a very small leap to VB.NET or C#.

ASP.NET apps also use the new ADO.NET data access method. This is a new way at
looking at data access, whether that data is in the form of relational database
tables or in the form of XML.

Because all of .NET development is based on OOP, you will need to develop a
mastery of OOP design and development.

A knowledge of XML, XSD and web services is also important when working with
any .NET technology, including ASP.NET.

I know it sounds like a lot, but it's a very powerful web development
environment.
 
yj said:
While both ASP and ASP.NET have
"ASP" in their names, they are very different. Just like C# and C++ sound the
same but are completely different languages and VB6 and VB.NET have similar
sounding names but are completely different languages.

ASP.NET is complete paradigm shift from the methodology and model of legacy
environments such as ASP. PHP and CGI.

ASP.NET is part of the .NET family of technologies. As such, it uses the over
3,400 framework classes that are available to anyone developing apps with
..NET.

Just a clarification:

Actually ASP.NET is part of the .NET Framework, which isn't really a family
of technologies but a new architectue on which .NET applications can run.
And, there are well over 10,000 classes defined within the .NET Framework
Base Class Library.

The code and presentation are completely separated (altho, someone who
develops using Notepad as opposed to one of the IDE's, may end up mixing the
code and the html onto the same page, the way old fashioned web development
used to be back in the ASP and CGI days -- this is not a good practice).

Programming is done with completely object oriented languages such as VB.NET
and C#. You can also use COBOL.NET, Perl.NET, J#.NET and managed C++. But
most people will be using VB.NET/C# (these two languages are so similar that
people routinely switch from one to another).

I think this is a matter of opinion. There are those who would say that
their syntax and feature sets are quite different.
If you plan to do ASP.NET development, you must learn one of these
languages. Keep in mind that while
 
Although, VB.NET sounds similar to VB 6.0 and ASP.NET sounds similar to ASP
3.0, they have major differences. I too came to .NET with a VB 6 and
Classic ASP background, but I'll tell you (now that I'm over the 'hump')
that it would benefit you to come into .NET without your VB baggage. That
is to say, don't think of the learning curve as what's new and what's
different. It may be better to think...It's all new, it's all different.

I like the WROX series and particular "Professional VB.NET 2nd Edition" and
"Professional ASP.NET 1.0".
 
Back
Top