The Future according to Asp+

As both an ASP and JSP programmer, I started a series of articles
To examine the differences between ASP and JSP. After I released
Part one and part four of the articles, asp+ is announced. asp+
Changes the game to the "point" I delayed writing additional
Articles until I could examine asp+ in greater detail.

I am currently working on a JSP project and on a separate ASP
Project.  The ASP project itself is very interesting. It is
Starting off in ASP 3.0 and would be translated to asp+ by time
The project is being done. As a result of this projects I'll be able
To examine asp+ closely, providing solid asp+ to JSP comparisons.

This article presents my early observations of asp+ and the impact
It has on a average developer such as myself.

In a initial comparison of asp+ and JSP I found the following:

1) Object Orientation:
Asp+ introduces C # as an object oriented language. In many respects
It would become Microsoft's version of a Java-like language. The
Other fun fact about C # is-that every object created automatically
becomes a COM object. What This all boils down to IS, if C # lives
Up to all or even 75% the marketing hype, it'll give asp+
Like capabilities but and faster performance due to its tight
Coupling with the Windows environment. C # is the ' single most
Important improvement for asp+ development.

Microsoft has engineered C # to be a stiff competitor of Java.
It is a major part of Microsoft ' s reinvention of their. Net
Framework. I-C # as Microsoft ' s push to is the dominant player
In the programming market place. I expect to the Microsoft put it
Full weight behind this product. As a result of "all", it ' s a
Safe Bet C # would become the language of choice for many programmers.

The consequence of C # would be the intensification of the battle
Lines between the Sun and Microsoft product lines. This actually
'll be of the benefit to the consumer, as it'll spur both Java
and C # to new improvements.

2) Database Connectivity:
The "one place" ASP really shines is in the use of the ADO
Object, ODBC, Ole-db and the Transaction Manager. Among all
These pieces it are very easy to builds fast and simple ASP
Database Web applications. Asp+ takes all this and marches onward
To even more features, while ado+ are being released with even
More enhancements and speed boosts. JSP and JDBC currently lag
Behind in ease of use and features when compared to the current
Implementation of Asp/ado. With the new release of asp+/ado+ the
Gap with JSP would widen even further. I personally hope SUN would
Put serious effort in catching up with asp+/ado+ combination.

3) Large Scale Sites:
Asp+ 'll have better support for large Web farms. In fact,
Microsoft is pushing this idea pretty hard. Asp+ wants
Terms of multiple servers. As you need, just
Add an extra server. The whole. Net Framework has solidly embraced
This methodology. Asp+ introduces external session state support
Providing built-in Web farm support. In addition, since all the
Components required to support a Web farm are built fully optimized
With each other, it would be fast. The end result is that asp+ would
Now equal JSP in the ability to scale to large projects. In fact,
Asp+ 'll have a cost benefit over JSP since all components
'll is part of the your server operating system from Microsoft. In JSP,
Currently need to purchase expensive Server application servers
To achieve similar results.

4) asp+ offers many other new features, that I'll review in the more detail
In future issues. For example,
*built-in Object Caching and page result caching.
*built-in XML support for easy handling of XML data sets.
*server controls which offer fuller interactive controls to
be used on the client page. Initial indications, however,
Show this are costly items in terms of round trips to use.

I am finding that asp+ truly expands what be possible in ASP.

My preliminary conclusion, after looking in asp+, is the majority
Of my future projects'll still be Java and JSP based. The three
Reasons for this are:

1 to really unlock the full potential of asp+ your'll need to use
C # or vb.net. These two languages would become the standard
Scripting Heart of asp+.

This is a good thing for the future of ASP. I never liked
Building COM objects in the current version of Visual Basic.
The new scripting heart of asp+ is a substantial improvement
Over ASP and would really energize the possibilities of web
Applications built within asp+.

All of the new development in asp+ are making it clear I need
To make a personal decision to choose the language into which I
Desire to put the most time and effort. I learned Java back when
It all started and I feel Java are a language that would be around
For the rest of my programming career. As a result, the JSP is my
Primary choice for Web development. When I current ASP project is
Done, I'll reconsider if C # convinces me to re-gear my programming
Tool belt. As I am now the big JSP fan, if Microsoft converts me,
It has a real winner! I suppose I am taking the asp+ challenge.

2) asp+ is still pretty squarely locked to Microsoft ' s operating
System. JSP has a major edge over asp+ in it flexibility to work
On the other server configurations. Keeping in mind, however, the
Rising predominance of the Windows operating system, this
Won ' t be a problem for many developers.

3 I am not sure if I agree with aspects of the new asp+ architecture.
I need to perform a more in-depth analysis on several issues before
Feeling comfortable with asp+. As a result, I am hesitant to?
Using it for future projects. This I have used it
For a month or two. After all, this is a high level overview of a
Beta product. I'll provided more information in a future in-depth
Review of Asp+.

As a ASP developer, asp+ gives me pause to. The next eight
Months are going to being a hard time to start a new ASP project. Why?
Asp+ and C # introduce a dilemma for development shops as they ' t
Available yet and won ' t be introduced until the ' a '
2001. This means if your are starting a new project now are
Faced with some seriously hard choices. I am in charge of setting
Up the technical aspects of such projects and appreciate
Considerations.

Since asp+ is only available as beta software it makes my
Choice easier. My current project would start in ASP 3.0. I consider
Any beta language to being vaporware until the production release is
Available.

I cannot ignore asp+, however, as in six months it would be available
And it represents the future of ASP. Managers of ASP projects in
Production now or in the near future should consider
Migration to asp+ would occur as smoothly as possible. While a savvy
Design would ensure a smooth upgrade to asp+ with the cost for development
Increases as extra time are spent in creating and implementing the
Design, as as the implementing the upgrade. This approach is sensible,
However, to prevent even higher costs over the long term when the final
Upgrade does happen.

A side effect of all's that it makes both PHP and JSP
Attractive alternatives to ASP for the near future. After all,

1 to the use asp+ you'll need some extra time to learn new tools.

2) The new tools are still to is released, so why don't look at
Something that currently exists?

3) JSP already has many of the new features of asp+.

4) asp+ locks you microsoft-only architecture.
(I have read one news story about Microsoft porting. Net to
Linux, but I discount this as being unrealistic in this
Point in time. Until The code is released, it fits in my
Vaporware category.)

As a result, I predict quite a few people'll make the leap into PHP
and JSP. However, I also feel many people'll stay the course due to
The sheer excitement that asp+ brings to the field. (I have never seen
Such an explosion of material to any beta programming product). Below
is a vs.net article which nicely illustrates both of these points.

For something so started as freeware, asp+ has grown to become a
Cornerstone the Microsoft ' s. Net framework. Sun may find a lesson in
This. Extra caution and care, however, is warranted when upgrading
To asp+ as it's being integrated with so many
The overall size of the. Net framework is so large. I usually wait
For the the ' the ' the ' the ' the ' the ' the ' the ' any product before assuming it
To use in a production environment. So, even if asp+ are released in
The quarter of 2001, for planning purposes, I am not expecting
Asp+ to is ready for my production environment until second
of 2001. Of course, since asp+ has generated so much excitement, many
Shops would switch over to asp+ as soon as it becomes available. In fact
I have already come across ASP Web sites using the beta release asp+!
For example, the link to the asp+ site I reference below are written in
Asp+, can tell by the. aspx extension. All this suggests to me
That is, Microsoft'll release the The "the" the "the" the "the" the "the" the

The next year is a very interesting time to watch the marketplace,
How Sun and Microsoft react to the current situation and what choices
Programmers'll make.


ADDITIONAL REFERENCES

The vs.net(DevX 9/2000)

FAQ on asp+(aspfree.com)

Another View on. Net(Jim Farley 8/2000) (A very good analysis of. Net)