What comes after ASP.NET?

  • Thread starter Thread starter Trevor Oakley
  • Start date Start date
T

Trevor Oakley

As I am learning ASP.NET from some books, I find that many books are
out of print. I have seen this trend before, and this signals a
replacement in techonology. It is very difficult to find many ASP
books nowdays.

I have no idea what is replacing ASP.NET, is it wireless (eg WAP,
WML), or something else?
 
While ASP.NET is not entirely new (been in public release coming up on 3
years now), it is hardly ready to be replaced with something else.

As you learn more about what ASP.NET and the .NET Framework is, you'll begin
to realize that ASP.NET is not a programming language, nor is it a product.
It is (as was classic ASP) an architecture. That architecture depends on
the .NET Framework and the .NET Framework has already seen one update and is
getting ready for another (Whidbey).

There are no plans to replace ASP.NET at all. But as with all software,
updates/upgrades will happen.
 
Hi,

I think ASP.NET is here to stay for at least the next 3 years. Most of
Whidbey (the next version of CLR/Visual studio) changes/ additions are
in ASP.NET. Although, Longhorn (MS new OS) might switch back developers
to Client / server programming we need to wait 3 years to see it kicking
and biting.

Natty Gur[MVP]

blog : http://weblogs.asp.net/ngur
Mobile: +972-(0)58-888377
 
Thanks for a speedy reply

I only mean that I want to learn something and implement something which is
going to still be useful in 12 months from now.

I have seen so many technologies come and go, and when they come many say it
is a revolution and then it vanishes 12 months later. I remember very well
when IBM invested vast reources in DB2 saying it was going to change all
database work, and combine it with a new integration architecture. Prior to
then we had non-relational databases. It was about 2-3 years later that
ORACLE had removed DB2 from the market. Abode announced SVG as a challenger
for Flash, and little SVG is used. IT markets are littered with hundreds of
similar tales.

I am aware .NET is a framework, but one limitation is that it hides much of
the raw programming from the developer, with validiator controls, datagrids
etc (I am talking about Visual C# which I am learning with ASP.NET). This
means that if changes to happen, developers dont have enough core
understanding to migrate to new languages.


..
 
Natty

By the way I eventually got my DLL's working (you replied about this to my
message). The host had to setup a virtual directory.

I was banging my head on a brick wall for 3 days over that.

Trevor
 
Trevor said:
Thanks for a speedy reply

I only mean that I want to learn something and implement something
which is going to still be useful in 12 months from now.

I have seen so many technologies come and go, and when they come many
say it is a revolution and then it vanishes 12 months later. I
remember very well when IBM invested vast reources in DB2 saying it
was going to change all database work, and combine it with a new
integration architecture. Prior to then we had non-relational
databases. It was about 2-3 years later that ORACLE had removed DB2
from the market. Abode announced SVG as a challenger for Flash, and
little SVG is used. IT markets are littered with hundreds of similar
tales.
Click to expand...

DB/2 removed from the market? I certainly don't work for IBM, and I dislike
all RDBMS anyway, but what market would that be???
 
ASP.NET hardly 'hides' any of the 'raw programming' from the developer at
all, especially compared to older technologies like classic ASP. Look at the
ways you can roll your own server side controls for an example.

Virtually every aspect of the ASP.NET pipeline can be extended or replaced.
 
I only mean that I want to learn something and implement something which
is
going to still be useful in 12 months from now.
Click to expand...

I know what you meant. ASP.NET will be here for years, just as its
predesessor (ASP) was (and still is).
I have seen so many technologies come and go, and when they come many say it
is a revolution and then it vanishes 12 months later. I remember very well
when IBM invested vast reources in DB2 saying it was going to change all
database work, and combine it with a new integration architecture. Prior to
then we had non-relational databases. It was about 2-3 years later that
ORACLE had removed DB2 from the market. Abode announced SVG as a challenger
for Flash, and little SVG is used. IT markets are littered with hundreds of
similar tales.
Click to expand...

There will always be competing technologies, but .NET is what MS has
declared as its programming paradigm going forward. They've spent years
developing .NET and "The .NET Platform" is still being implemented by
incorporating .NET into the OS and the Enterprise Servrer line. If you work
with MS software solutions, .NET is the CORE of the programming model. They
are not about to abandon it before it's even fully implemented. MS has no
public plans for something that will replace .NET.
I am aware .NET is a framework, but one limitation is that it hides much of
the raw programming from the developer, with validiator controls, datagrids
etc (I am talking about Visual C# which I am learning with ASP.NET). This
means that if changes to happen, developers dont have enough core
understanding to migrate to new languages.
Click to expand...

I totally disagree. The raw code is totally open as never before. When you
update your version of the framework, you don't lose the older version (if
you go to 1.1, you still have 1.0). This ensures that applications written
using the 1.0 framework will still have a way of running even when there is
a 4.0 framework.
 
The current architecture is OOA (object oriented architecture) and
computer scientists have discovered its economy and its limitations
some time ago by using SmallTalk and Eiffel on a sufficient number
of projects both large and small to gain such a body of knowledge.

For example, C++, C#, J#, Java are contemporary languages that
are used to conduct OOP (Object Oriented Programming).

ASP.NET requires OOP and will remain viable in my opinion for
at least 3-5 more years. However...

Microsoft is in fact already at work using new architectures.
People that are future oriented should spend time at
http://research.microsoft.com/.

It seems to me that the next architecture will enable what seems
to be referred to as 'functional' programming but describing it
beyond that is a body of knowledge I have no knowlegde of.

Just learning to become masterful with an OO architecture using a
language such as C# with a framework such as the .NET Framework
is enough to keep me busy for the next 3-5 years.

--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET (e-mail address removed)
URL http://www.metromilwaukee.com/clintongallagher/
 
Joerg Jooss said:
DB/2 removed from the market? I certainly don't work for IBM, and I dislike
all RDBMS anyway, but what market would that be???
Click to expand...
You appear not to remember the 1980's. At the time IBM made a big play
for the emerging database market and it badly misread it. IBM invested
vast amounts of money in DB2, and in London DB2 experts were earning
£5000 ($10000) a week. It was very short lived. Two years later people
had almost entirely dumped DB2. ORACLE bounced into the market and
also a range of PC databases such as Foxpro.
 
Ed Courtenay said:
ASP.NET hardly 'hides' any of the 'raw programming' from the developer at
all, especially compared to older technologies like classic ASP. Look at the
ways you can roll your own server side controls for an example.

Virtually every aspect of the ASP.NET pipeline can be extended or replaced.
Click to expand...

What I mean by my comment, is that ASP.NET combined with Visual C#
hides a lot of the programming. Developers can work with the IDE and
use a series of menus, changing small lines of code inside methods.

ASP is very weak language, more like a script.
 
Technologies come and go. Sure, it's difficult to ride the current wave and
keep up with the changes, but there are plenty of jobs for programmers who
don't want to keep up, managing legacy systems, if that's a problem.
Sometimes I get tired of bleeding on the bleeding edge of things, but what a
view!

--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
 
What I mean by my comment, is that ASP.NET combined with Visual C#
hides a lot of the programming. Developers can work with the IDE and
use a series of menus, changing small lines of code inside methods.

ASP is very weak language, more like a script.
Click to expand...


I'm sorry, but that's just sooooo wrong. It's obvious you haven't spent
much time with VS.NET/ASP.NET. Virtually all the code is available in
VS.NET for the programmer to modify.
 
Scott M. said:
I'm sorry, but that's just sooooo wrong. It's obvious you haven't spent
much time with VS.NET/ASP.NET. Virtually all the code is available in
VS.NET for the programmer to modify.
Click to expand...

I have not used ASP.NET much (about 2 weeks).

It is a comparative to say code is hidden. I am comparing Visual C# to
C, Assembler, COBOL, and others. Ultimately Visual C# is just
generating Assembly code; this is even viewable in the IDE.
 
Back
Top