views:

217

answers:

1

Curious about things to consider to avoid any code breaks, etc to upgrade from .NET 3.5 to 4.

I am particularly interested in: - What would be the server requirements to deploy a .NET 4 app? Does it need any particular version of IIS and Windows Server to run?

I am facing serious performance issues with Entity Framework due to the large size of database and initialization takes long time for the first user to login. .NET 4 seems to realize this as a widespread issue and has something called PreWarm apps. Scottgu's post here seems to talk more about it. But, curious if this will work on IIS 6 and WinServer 2003.

Are there any other things i need to think of before making the switch to .NET 4?

+1  A: 

.NET Framework 4 Beta 2 can be installed on Windows Server 2003. The software requirements are:

Supported Operating Systems: Windows Server 2003; Windows Server 2008; Windows Vista; Windows XP

.NET Framework 4 can be installed on the following operating systems:
- Windows XP SP3
- Windows Server 2003 SP2
- Windows Vista SP1
- Windows 7
- Windows Server 2008 (not supported on Server Core Role)
- Windows Server 2008 R2 (not supported on Server Core Role) Note that .NET Framework 4 is currently in Beta. If you have a working app on production, you might want to consider waiting for its RTM.

Mehrdad Afshari
@Mehrdad: Thanks dude. How about support for IIS6? My current production environment is IIS6 and Win2003. I am trying to understand, if i can take full potential of .NET 4 on my current environment or will it require upgrade IIS7.
pencilslate
Well, you can use almost everything in .NET 4 in IIS6 too. Of course, you cannot use newer IIS7 features that take advantage of .NET like Integrated mode. For the most part, it's OK.
Mehrdad Afshari