-boRg- wrote:
The problem is that classic ASP is no-longer being developed. |
True. At some point I may consider ASP.NET for a new website, but I am not going to convert an existing thousand plus page website to ASP.NET just because its the latest greatest thing. If my website works fine in ASP and does what I need, there is no reason to switch to ASP.NET.
So, as a paying customer, basically I will always upgrade to the latest ASP version of WWF. But if development of the ASP version stops, then I'll just have to take over the maintenance of WWF on my website rather than convert to ASP.NET.
My website wouldn't benefit from any of the new features of ASP.NET anyway. So why go through all the trouble of rewriting everything?
-boRg- wrote:
Although at the moment it looks like the downloads for ASP forums still out weighs the downloads for ASP.NET forums more and more people are moving across everyday. |
Partially that is because of the large ASP userbase. ASP Classic is not going away anytime soon. Hell, people are still using Perl when there are more modern languages like ASP/VBScript, ASP/JScript, PHP and ASP.NET.
Even if Microsoft stops supporting it, there is always Chilisoft which allows you to run ASP in Linux. It may become less popular over time, like Perl, but it will never go away.
-boRg- wrote:
I've been looking at ASP.NET version 2 and it looks like there are quite a few improvements. Also allot of things like simpler to do in ASP.NET as they are built into the framework, rather than having to spend hours, if not months sometimes developing work arounds in ASP. |
ASP.NET does seem to be the next generation of web design, so I am sure many new projects will get developed in it due to that simplicity. I am even considering trying it out myself. But, again, for new stuff only. Converting old stuff that works is a waste of time.
-boRg- wrote:
One things that puzzles me is why everyone who develops ASP.NET software always releases it as a .DLL file, even the free stuff.
This makes modifying the code and learning from other developers code impossible, which is something I would rather stay away from. |
Agreed. They probably do it so you have to pay them at some point to update they code.
I won't use any code on my website that I do not have the source code to. Period.
I made that mistake once, and wound up rewriting all their poorly written ASP.NET DLLs into ASP Classic so I could fix them and enhance them. I asked for ASP Classic, they gave me ASP.NET DLLs. I was not happy.