I am working on the asp.net 2.0 application. During the opening of the application in VS 2010, the application was developed in VS-2005 and changes were needed to open VS-2010.
Now that I see that the wizard has differentiated it is mostly for * .sln, * .csproj, * .designer.cs. Therefore, these changes are safe to check, because all developers are using VS2010. Is it only the visual studio effect and it breaks any existing functionality?
Previous .csproj file Modified .csproj file Previous *. Designer.cs. [Global :: System.CodeDom.Compiler.GeneratedCodeAttribute ("Microsoft VisualStudio.Editors.SettingsDesigner.SettingSingleFileGenerator", "9.0.0.0")] / Pre> Modified *. Designer.cs.
& lt; Project Tools version = "3.5" default target = "build" xmlns = "http://schemas.microsoft.com/developer/msbuild/2003" & gt;
& lt; Project Tools version = "4.0" default target = "build" xmlns = "http: //schemas.microsoft.com/developer/msbuild/2003"> & Lt; FileUpgradeFlags & gt; & Lt; / FileUpgradeFlags & gt; & Lt; OldToolsVersion & gt; 3.5 & lt; / OldToolsVersion & gt; & Lt; Upgrade Backspace / & gt;
[global :: System.CodeDom.Compiler.GeneratedCodeAttribute ("Microsoft.VisualStudio.Editors.SettingsDesigner.SettingsSingleFileGenerator", "10.0.0.0")] < The only reason for the warning is that the post-conversion project is VS2005 (or 2008 for that case) Can not be opened in If your remaining shop is in 2010, and the post-conversion project makes it successful for you, it will not be a problem for anyone else.
No comments:
Post a Comment