callistra.moonshadow writes: At my company we have put in a service request to roll out the
.NET Framework 3.51. Several new applications leverage LINQ for database components in our applications. We currently have a mix of classic ASP, .NET 1.0 and 2.0 applications as well as some old Cold Fusion on our web servers. The powers that be that maintain the web servers do not want to complete the service request because "It will cause problems with the 1.0 and 2.0 frameworks." Now 3.51 is an expansion of the 2.0 applications and is backwardly compatible. If the code is already compiled (should be in production but our server admins are not all that) no problem. If not the case it should still not be a problem as the code should recompile on the web server. 1.0 framework should not be an issue as it is totally separate. One thing I DO know is that the network admins are not using the recommended separate application pools. I am not sure why, but I suspect it's a lack of understanding on how to set it up. Well they are fighting us because they claim they would break a number of applications. There is a LINQ extension for 2.0 but to the team this seems foolish. If anyone has some wisdom here I'd really appreciate it.