.NET Tutorials, Forums, Interview Questions And Answers
Welcome :Guest
Sign In
Win Surprise Gifts!!!

Top 5 Contributors of the Month
Gaurav Pal
Post New Web Links

Upgrading .Net 2.0 to 3.5 (Compatibility Issues)

Posted By:      Posted Date: December 04, 2010    Points: 0   Category :.NET Framework


I am responsible for a college webserver (Windows Server 2003 Enterprise Edition SP2 with IIS 6.0 and .NET Framework 2.0) It hosts over 100 webstes on it.

There has been request for support .NET 3.5 for new websites. If we accept support for .NET 3.5 I will need to upgrade to .NET 3.5 and there starts my worries. How would it effect other websites running 1.1 and 2.0 versions of them on the server. In case of upgrade what should I do to maintain these sites working and if things go wrong s this upgrade operation reversible? I mean can I just uninstall .NET 3.5 and would everything go back to current state?

I have been looking up in google for a while I guess I have to test this out but I have no idea how can I test it? Do I need a new system setup of  MS Windows 2003 and move the sites and test them with . NET 3.5 Since there are so much sites and databases it seems even more frightful to do this. If I need  to test how would you suggest to test?

And finally is there a way I can get a list of which sites use which . NET ersion and which doesn't (There are also a lot just static html sites)

I know I asked a lot but I am really nervous about it if this upgrade would mess the server. And yes as you can understand from what I ask I am more of a rookie about these so the information I can get is very crucial for me.


View Complete Post

More Related Resource Links

MSSQL Server 2008 Workgroups install to Win 7 - Compatibility issues

I attempted to install MSSQL Server 2008 Workgroups from the DVD to a Win 7 workstation.  Error "This Program has known compatibility issues.  The directions are to download the MSSQL Server Service Pack.  I downloaded SP 1 and SP 2.  Neither SP will install.  The DVD install also has a run option displayed along with the Compatibility message.  I select "Run" and it appeared to install, with Start\Programs\Microsoft SQL Server 2008\Configuration Tools\ SQL Server Installation Center 64bit.  However, running the 64bit installation process results in no change.  My question is how to install the MSSQL Server 2008 Workgroups on the Win 7 machine.  I would appreciate your thoughts.

MSSQL Server 2008 Workgroups install to Win 7 - Compatibility issues

The DVD install for MSSQL Server 2008 Workgroups to Win 7 fails due to known compatibility issues.  I asked for help in the Getting Started with SQL Server Forum and followed a recommendation to slipstream installation with SP1. I followed the procedures at http://blogs.msdn.com/b/joaol/archive/2009/03/20/how-to-install-sql-server-2008-with-sp1-built-in-slipstream-installation.aspx I then ran Setup.exe from the C:\SQLServer2008 folder.  It failed with the following .Net Framework error.  (I previously installed .Net Framework Version 4 which is required by the application needing SQL Server.)  Thanks for help. Microsoft.NET Framework Unhandled exception has occurred in your application.  If you click Continue, the application will ignore this error and attempt to continue.  If you click Quit, the application will close immediately. An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System. Version= PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. (C:\users\PC User\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thcltsvyyx\\user.config line 5). Details... See the end of this message for details o

What compatibility issues present with MOSS 2007 and Office 2010?

We have been running MOSS 2007 for a year now and recently upgraded office workstations to Office 2010.  I am trying to research what compatibility issues might be experienced with this match of products.  Thank you for any examples.

Getting User related issues when Upgrading Classic based 2010 web application to claim based 2010 we



I have upgraded Classic based to claim based . I used these Power-Shell scripts :

$w = Get-SPWebApplication " http://<server>/ "

$w.UseClaimsAuthentication = 1




It upgraded fine. But I am getting a problem when users are trying to log in, they are not able to log in to sharepoint. When I remove existing user and add the same user again then that user can log in.

One thing I also noticed that If User "ABC" is already in Share Point and If I add same user again then it shows both users. But there is only one user.

I am using Share Point 2010 RTM.

What is wrong with my share point 2010?

Can you please help me ?

G. Goyal

Compatibility issues between Microsoft Visual Studio 2005 and Windows Server 2008 R2


Dear sirs,

When I was installing SQL Server 2005 64 bit on Windows Server 2008 R2, I received a notice informing the software Microsoft Visual Studio 2005 has known compatibility issues with this version of Windows.

So how can I get around these problems?

I need to use Visual Studio 2005 to create the Integration Services packages.

Also, I need to migrate directories of Integration Services packages from a server with SQL Server 2005 32 bit on Windows Server 2003 32 bit for a server with SQL Server 2005 64 bit on Windows Server 2008 R2. How can I proceed to do this?

Thanks in advance.

Jose Luiz

Problem upgrading to MVC3 - System.Web.Routing



I'm trying to upgrade to .NET 4 and MVC 3.

When trying to compile my project, I get the error:

Error 1 The type or namespace name 'Routing' does not exist in the namespace 'System.Web' (are you missing an assembly reference?) C:\Users\spencer\Desktop\weblauncher\Common\MVCConfig.cs 4 18 Common

The type or namespace name 'Routing' does not exist in the namespace 'System.Web' (are you missing an assembly reference?)

I do have the System.Web.Routing in my references for the project.

BUT - when I try to view System.Web.Routing in the OBJECT BROWSER, nothing is inside!  The System.Web.Routing namespace is not in there - the entire thing is empty!  Could it that the dll is corrupted?  I tried to reinstall the .NET 4 and MVC 3 stuff, but its still empty!

The dll is coming from here:

C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.0\System.Web.Routing.dll

and the runti

UpdatePanel is not a known element - message when upgrading to 1.0 ajax


It worked on one of my old pages.  I change the web.config, renamed all the <asp.

On some aspx page it doesn't recognize the updatepanel.  It only does on one page.  If I create a new aspx page with a different name - then it works.

Should I just create a new web project ajax - then copy all my code into there?  Or is there a way to get those old pages to recognize the new ajax controls?

Error upgrading SQL Server 2008


i was normally using VS2005 and SQL server 2005...

i upgraded to SQL Server 2008... and then...

i could not build my project anymore... because of this error:

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 
Exception Details: System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)
Source Error: 

IE 8 Issues with Chinese/Japanese Characters


On my web application, I display information in different languages. Everything works fine in IE compatibility mode and FireFox but it shows boxes for chinese/japanese languages. I am pretty much having the same issue as described here



Thanks for your help.

Reporting Services SQL 2005 .Net 4 compatibility?


I've been working on my first asp.net application and for the most part it's been pretty smooth.  Right now I'm having trouble getting reporting services working under SQL Server 2005.  I developed the site with Visual Studio 2010 and didn't think about any of the .Net 4.0 compatibility issues that have arisen.  I'm having no problems with the site communicating with SQL Server 2005 for the regular database stuff.  The only problem I'm having is with setting up Reporting Services.  I have the .Net 4.0 framework installed on the server, however Reporting Services is still using 2.x.  I'm not sure if this is a problem with SSRS or with IIS.  When i go to localhost/Reports it's reading my web.config for my application and throwing an error: "Parser Error Message: Unrecognized attribute 'targetFramework'."  This is referring to a line in my web.config where targetFramework is set to 4.0.

Software that I'm using:

  • Visual Studio 2010
  • SQL Server 2005 Standard
  • IIS 7.0
  • .Net 4.0

Any suggestions?  

Concurrency: Tools And Techniques to Identify Concurrency Issues


Efficient parallel applications aren't born by merely running an old app on a parallel processor machine. Tuning needs to be done if you're to gain maximum benefit.

Rahul V. Patil and Boby George

MSDN Magazine June 2008

CLR Inside Out: Investigating Memory Issues


Memory issues can manifest in a wide variety of ways. This column shows you how to collect the data you need to determine what types of mem¬ory issues you are experiencing.

Claudio Caldato and Maoni Stephens

MSDN Magazine November 2006

CLR Inside Out: Ensuring .NET Framework 2.0 Compatibility


If we learned only one thing about compatibility in the past few years, it is that compatibility is much more than avoiding breaking changes. On the Microsoft®. NET Framework and Visual Studio® teams, we do our part to ensure that the products we build are stable platforms that developers can truly rely on.

Jesse Kaplan

MSDN Magazine March 2006

Stress Testing: Custom LoadGenerator Tool Identifies the Issues Your Application Faces Under Stress


It's easy to postpone stress testing when developing an application, and it's easy to forgo it altogether. Having an easy-to-use framework at your fingertips to conduct these tests can make the task far less painful. This article walks you through an application that eases the task of generating load for a variety of layers within an application.

Brian Otto

MSDN Magazine April 2004

Versioning Issues With Optional Arguments

One nice new feature introduced in C# 4 is support for named and optional arguments . While these two features are often discussed together, they really are orthogonal concepts. Let's look at a quick example of these two concepts at work. Suppose we have a class with one method having the following signature. // v1 public static void Redirect( string url, string protocol = "http" ); This hypothetical library contains a single method that takes in two parameters, a required string url and an optional string protocol . The following shows the six possible ways this method can be called. HttpHelpers.Redirect( "http://haacked.com/" ); HttpHelpers.Redirect(url: "http://haacked.com/" ); HttpHelpers.Redirect( "http...(read more)
ASP.NetWindows Application  .NET Framework  C#  VB.Net  ADO.Net  
Sql Server  SharePoint  Silverlight  Others  All   

Hall of Fame    Twitter   Terms of Service    Privacy Policy    Contact Us    Archives   Tell A Friend