ASP vs. ASP.NET
Peter Bernhardt
there's a lot out there) but I'm looking specifically for something that
makes a convincing case for moving exisitng ASP applications to ASP.NET.
From a business rather than a strictly technical perspective. As if I were
a decision maker in a small company with an existing ASP site -- what is it
about ASP.NET that would convince me to go to the expense of updating that
site to ASP.NET?
Again, I've found some articles already, I'd just appreciate learning from
others what their favorites might be.
Thanks in advance.
--
Peter Bernhardt
pe...@SharpSense.netBASURA
**************************************
Remove that spanish word for trash to reply direct
**************************************
Steve C. Orr, MCSD
ASP?
That should save on hardware costs!
http://www.directionsonmicrosoft.com/sample/DOMIS/update/2002/01jan/0102aidowa_illo3.htm
(Not to development all the software development time saved from a
friendlier and more powerful programming environment.)
--
I hope this helps,
Steve C. Orr, MCSD
http://Steve.Orr.net
"Peter Bernhardt" <pe...@SharpSense.net> wrote in message
news:O4KvBgXF...@TK2MSFTNGP10.phx.gbl...
Joe Iano
and it's going to be a lot of work. The only way I can see to justify this
is so as to maintain compatibility with new development technology. In other
words, moving forward with this application, do I want to forever continue
to code in vbscript/asp, or in the long run, will I get better return on
investment working in c#/.net. If it were mainly a concern about
performance, upgrading hardware would be much much less expensive for us
than upgrading/porting code. If I didn't expect the code to continue to
evolve, I would leave it in classic asp.
"Peter Bernhardt" <pe...@SharpSense.net> wrote in message
news:O4KvBgXF...@TK2MSFTNGP10.phx.gbl...
Brian Staff
> ASP?
I have a lot of experience in ASP and some in ASP.NET (C#) and I don't yet see any benefit
to dotNET and certainly not 3 times better (faster???). Mind you I don't have 4000 lines of
C# code in my pages either. I can't imagine what 4000 lines of C# does for one page anyway.
I would say if his ASP pages are working well with good performance then leave them alone.
From my position, I see ASP.NET as being a lot of work due to a lot of hype.
Brian
Kevin Spencer
HTH,
Kevin Spencer
Microsoft FrontPage MVP
Internet Developer
http://www.takempis.com
Six of One of half of
One of a dozen of the Other.
"Brian Staff" <brianstaff@[NoSpam]compuserve.com> wrote in message
news:VA.00000203.0b206b99@bstaffw2k...
Parker Zhang [MSFT]
ASP.NET provided:
- Improved Performance and Scalability because of Compiled Execution,
Rich Output Caching, Web Farm Session State
- Enhanced Reliability because of Memory Leak, Dead Lock, and Crash
Protection
- Easy Deployment because of "No Touch" Application Deployment, Dynamic
Update of Running Application, Easy Migration Path
- Developer Productivity because of Easy Programming Model, Flexible
Language Options, Rich Class Framework.
Therefore, it is recommended to migrate from ASP to ASP.NET
--
Parker Zhang
Microsoft Developer Support
This posting is provided "AS IS" with no warranties, and confers no rights.
Jens
see any benefit
> to dotNET and certainly not 3 times better (faster???). Mind you I don't
have 4000 lines of
> C# code in my pages either. I can't imagine what 4000 lines of C# does for
one page anyway.
> I would say if his ASP pages are working well with good performance then
leave them alone.
>
> From my position, I see ASP.NET as being a lot of work due to a lot of
hype.
>
> Brian
Apparantly, you have never developed a serious Web Application ...
I would not go back to ASP even if they payed me big time for it ...
Jens
>
>
>
Justin SB
ASP.NET easy (by allowing ASP and ASP.NET to share sessions).
We have a white paper that titled "Moving to ASP.NET" that may be what
you're looking for.
http://www.consonica.com/information/index.html
Here is the table of contents:
Promises of ASP.NET
· ASP.NET facilitates the development of complex applications
· Web Services are heavily marketed but remain a long-term
proposition
Benefits For Developers
· WebForms accelerate basic web-programming tasks
· .NET helps produce best-practice systems
· ASP.NET delivers a full spectrum of services
· Built-in support for Authentication and Caching
Benefits for Web Administrators
· .NET technology simplifies the administration of websites
Realities of ASP.NET
"Choice" of Languages (.as long as it's.)
· Supposed wide choice of programming languages is illusory
· Most ASP.NET code will be written in VB.NET, C# or J#
· .NET languages offer sophisticated new features
Session Support - and the Session Problem
· Sessions are used to store user information on the web server
· ASP.NET sessions now work across web-farms
· Special solutions are required to share Sessions
Difficulties in Moving to ASP.NET
Developers will not be familiar with .NET
· .NET demands more from developers
· Code quality must be considered
Migrating existing applications to ASP.NET
· ASP.NET is similar to ASP, but they are not compatible.
· Full coexistence of ASP and ASP.NET requires Session-Sharing
Migration Strategies: From ASP to ASP.NET
Key Considerations
· Lack of .NET experience demands careful management
· Rewriting code should be avoided
· .NET is supposed to solve problems, not create them
Strategies that do not depend on Session Sharing
Strategy: "Big Bang" - Rewrite entire application in ASP.NET
Strategy: "Hall of Mirrors" - Convert to ASP.NET syntax
Strategy: "Peeling the Onion"- Move One Layer at a Time
· Avoid strategies that do not depend on session sharing
Strategies that depend on Session Sharing
· Sharing Sessions enables better strategies
Strategy: "Page at a Time"
Strategy: "Lifecycle"
Strategy: "Phased Lifecycle / Page at a Time"
Summary - Comparison of Migration Strategies
The best strategies use Consonica's StateStitch tool for Session-Sharing
About Consonica's StateStitch Tool
Glossary
Justin Santa Barbara
Consonica
StateStitch Enables Seamless ASP to ASP.NET Migration
"Peter Bernhardt" <pe...@SharpSense.net> wrote in message
news:O4KvBgXF...@TK2MSFTNGP10.phx.gbl...
Brian Staff
> Apparantly, you have never developed a serious Web Application ...
> I would not go back to ASP even if they payed me big time for it ...
hmmm! does it have to big to be serious?
get serious!<g>
Brian
Steve C. Orr, MCSD
me tons of time! It is superior and more efficient in nearly every way.
Think about a typical input page with a bunch of textboxes on it and a
dropdown list or two. Even a basic page like that is so much easier because
you don't have to worry about repopulating the data in all the controls
between each postback, and if you have a few data validator controls on the
page then you've got complete client side AND server side validation done
for you automatically. How long would it take you to create a page like
that in ASP.OLD? A lot longer than the few minutes it takes ASP.NET, I can
tell you that.
--
I hope this helps,
Steve C. Orr, MCSD
http://Steve.Orr.net
"Brian Staff" <brianstaff@[NoSpam]compuserve.com> wrote in message
news:VA.00000206.1122152b@bstaffw2k...
Admiral Bob
> Apparently you don't need all that extra power.
>
> HTH,
>
> Kevin Spencer
> Microsoft FrontPage MVP
> Internet Developer
> http://www.takempis.com
> Six of One of half of
> One of a dozen of the Other.
Or more to the point, without a migration path forward (no tool of any
sort was provided, and most code breaks when switched), one has to
decide whether one leaves existing ASP apps in place and works on new
projects, or one has to try and explain to the CEO why all new
software application development will cease for a time while a geeky
migration process inexplicable to most laypeople takes place.