Aside from other issues that have been addressed nobody said anything --
yet -- about a "better experience" that is much easier and user friendly to
implement when using ASP.NET 2.0. The use of MasterPages and Themes for
example allow broader support allowing visitors to the website to
personalize their experience. The use of Web Parts also supports user
expereince in that it allows users to drag and drop page elements they
prefer. That's the keyword in fact: preferences, which is fundamental to the
user experience.
This may be a very important issue to you in the UK as I understand the
government has gotten serious about compelling website publishers to make
their websites accessible to people with visual and other impairments.
ASP.NET 2.0 makes great strides in this area too.
ASP.NET 2.0 supports Membership, Roles and Profiles which make coding
authentication and access to pages and resources quite productive.
Hands down ASP.NET 2.0 improves functionality and provides a much better
experience than ASP/VBScript web development but learning ASP.NET is time
consuming as is the initial design and setup of applications. After that
however it reapidly becomes a much easier and faster to use. Nobody would go
back to ASP without being dragged kicking and screaming.
--
<%= Clinton Gallagher
NET csgallagher AT metromilwaukee.com
URL
http://clintongallagher.metromilwaukee.com/
<ia**@isluk.demon.co.uk> wrote in message
news:yY**************@isluk.demon.co.uk...
Forgive me if this is the wrong place to ask this. I have a large
application written in ASP/SQL Server. I am not a programmer. The guy
who has written them for me is reluctant to move to .NET. I'm concerned
that he is not plugged into the development community enough and not up
with the latest developments. I'm worried also because I could be missing
out on:
* productivity gains
* additional functionality
* a better experience for my users.
* and....
1) I would like people's views on the above.
a) Why the reluctance?
b) What benefits could I really expect from moving from ASP to .NET?
2) I would like to know what problems/issues are involved in moving from
ASP to .NET.
Thank you.
--
Ian Whitfield