Perl vs ASP vs .NET vs PHP

www.asp.net has some tutorials on migrating asp to asp.net.

Any system development effort has three factors pressuring it

• cost
• quality (read quality/functionality/reliability/performance, - all the stuff that makes it a "good" or "bad" app)
• time

Typically, you get two out of three. (low cost but spend a lot of time to build quality; buy components to reduce time = high cost+good quality; low time developing plus low cost = low quality). Ideally you want to spend low time and low cost to get high quality. Asp.net's approach to this is through reuseablity.

The trick to migrating to new technology is not do it all at once, but concentrate on where you'll have impact upon your development process.

I've found it useful to think about how my app does things rather than what it does and run against cost-quality-time to see what I need to improve on. All apps perform certain functions. I evaluate those funtions for my particular app to see what can be done with new technology to mprove my development/maintenace of them.

For converting asp apps to asp.net, in general, things useful to look at are how security is handled, forms processing, input validation, email, data access, etc.. The code you put into improving one of these areas is generally pretty reuseable in other apps. Typically, these areas can be "cut out" of the app and placed into separate directory structures flagged as .net apps rather than as asp apps.

Some apps may have specific issues that could be done better to make maintenance easier - e. g. user updateable sections, multi-calendars, etc. When you look at your app, you'll be able to think of things that you could do to improve cost/quality/time for that specific app, and things that you could do within it that could be reusable.

Some parts of your asp app are just going to be solid. They don't change a lot, are complicated but work, have no performance issues, etc. My advice would be not to change them to asp.net. Doing so will have no impact on cost/quality/time to maintain your app or to develop new ones.

PHP isn't faster then ASP.NET

I hate people who just say they hate everything of MS without a really good reason. I mean, how many blue screens do you REALLY get? In fact, Win XP and some other MS stuff (ASP.NET) is really good.

almost every server runs a unix based OS linux/bsd/solaris/,... only the asp webservers use windows as their os and frankly they suck, some companies use windows because the employers are to "stupid" to use anything else.

There are quite a lot of ASP applications that are Open Source

a web application always has to be open source , how else can you change it to your needs
ps windows is closed source, and the virused for xp are countless just like the regkey's

but anyways, it has no point telling this to people who use mircosofts windows and havn't tried anything else