I have a few questions:
My company has about 40 mid-sized application written in class asp. We plan to upgrade to ASP.NET since Microsoft will no longer support ASP
in three years. As of today, most of our servers are running ASP.NET 2.0. Here are a few of the questions:
1.) Is ASP.NET 3.5 or ASP.NET 3.0 stable enough to be put to production?
2.) Can IIS run different versions of ASP.NET?
3.) For new applications, would you guys develop it in ASP.NET 2.0 or the latest version?
4.) Any known problems?
I love the the MVC and ORM/LINQ about ASP.NET 3.5; however, I'm satisfied with ASP.NET 2.0 + custom MVC + NHibernate.
Computer System Analyst
Go with 3.5. It's very stable. Its still the 2.0 clr so you really have no reason NOT to go with 3.5.
Yes, IIS if fine with multiple versions on a per-site basis. It's an option in the Asp.Net tab of the Site config in IIS.
I do everything in 3.5/vs2008 now.... and would never go back unless there was an absolute requirement.
Just out of interest where did you get the time frame from, I have seen lots of posts that back up this statement http://forums.iis.net/t/1149071.aspx
ASP.NET 3.5 is ASP.net V2 with a few features added, So no reason that you can not use it now in production, loads of sites are with no problem.
Each virtual directory can be mapped to a version of the framework.
Hope it helps
If this has helped Please: Don't forget to click "Mark as Answer" on the post that helped you.
That way future readers will know which post solved your issue.
Consider, we still have MS-SQL 6.0 in our production environment. Upgrading from ASP.NET 2.0 to ASP.NET 3.5 in five years sounds like a good guess to me. :-p
Computer System Analyst
I use 3.5 for my new applications or upgrades of older ones. 3.5 is 2.0 with some updates and it pretty stable. In IIS you can run different versions of ASP.Net but don't go looking for 3.0 or 3.5, you just use 2.0 (the CLR is the same).
Consider, we still have MS-SQL 6.0 in our production environment.
Seriously? Wow... I would have quit....seriously....
Yeah, me too o.O My last job was in .NET 3.5 and VS2008, but my current one is in .NET 2.0 and VS2005, and honestly, if it wasn't that they promised me the migration by the end of the year... Its such a huge step back.
Now unfortunately, getting people to upgrade to SQL Server 2008 is a lot harder... But SQL 2008 is LIGHTYEARS ahead of 2005, and seriously, I can't wait... if I had the choice between VS2008 and SQL Server 2008, I'd choose the later without thinking, haha... SQL 6.0... OUCH! thats brutal.