|
MadHatter ¢ wrote: they re-invented asp.net for 2.0, the cost of migration on that is too high.
I agree on that. I have a (not much) old ASP.NET 1.1 application. The migration would require rewriting a lot of stuff, so it stays 1.1.
But for new applications, I really like ASP.NET 2.0, especially Master Pages.
|
|
|
|
|
non-asp migration is a pretty arduous task, but I'd say asp conversion is a total waste of time (may as well re-write it).
it seems like they looked at "what would be the hardest thing for people to change?" then they depricated it.
|
|
|
|
|
Dario Solera wrote: migration would require rewriting a lot of stuff, so it stays 1.1.
Well, I've migrated some ASP.NET 1.1 apps to 2.0.
The migration wizard ran smoothly, and the only problem were with special characters I've had with files that wasn't UTF8. However, that took notime to fix, and I gain access to the (a-lot) better tools that 2.0 languages has (Generics, anonymous delegates, ?? operator, etc.), the 2.0 Framework (Membership, ASP.NET Controls, better System.Xml, Dynamic Methods) and the VS2005 which is a lot better than VS2003.
|
|
|
|
|
our asp.net apps contain hundreds of thousands of lines of code, and there are 4 or 5 of them. We did an initial migration and after a couple of weeks dropped it.
there is the physical migration that vs.net does, but after that there are a ton of logical, and api level modifications that have to be done, and the logical ones create huge potential breaking changes to our apps, that again will cost too much to 1. implement 2. debug and 3. migrate to production.
|
|
|
|
|
I hear great thing's about 3.5 ohh wait 4.0 it much better, and 5.0.........
|
|
|
|
|
Generics
Master Pages
Kevin
|
|
|
|
|
Generics, is obviously the most used and useful on the list but Master Pages are a godsend when having to write websites.
|
|
|
|