Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jan 03, 2013 09:40 PM by Careed
Jan 02, 2013 09:11 PM|LINK
I have installed VS2010 and opened my sln with Visual Studio 2010. The conversion was successful and the projects build successfully. The solution file was changed and each project file now has the following differences.
Old - <Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
New -<Project DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="4.0">
Old - <Import Project="$(MSBuildExtensionsPath)\Microsoft\VisualStudio\v8.0\WebApplications\Microsoft.WebApplication.targets" />
New - <Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\WebApplications\Microsoft.WebApplication.targets" />
I need to upgrade every developer so they can use VS 2010. Visual Source Safe is controlling the code. Any ideas on the best course of action to deploy? If I checkin the sln and project files the developers can check out and open with VS 2010, but would
I need to migrate these project files to Production? I am not upgrading the Framework at this time. thanks
Jan 03, 2013 12:33 AM|LINK
If all of your solutons/projects are contained within VSS, then you should be able to open the solution in VS 2010, allow for the conversion/upgrade, and then recommit back into VSS. After this, any developer should be accessing an upgraded solution. Additionally,
they should not be able to open these solutions in VS 2005 any more.
As for migrating to production, there should be no difference in your current process.
Jan 03, 2013 03:51 AM|LINK
Jan 03, 2013 01:53 PM|LINK
If you mean by "project files" all of the files used to support the process of being an application, then I would say that you should never put any of these files in production as this could be a potential security issue.
If this is not what you mean, please clarify.
Jan 03, 2013 02:27 PM|LINK
I mean the .csproj files. The changes in my initial post were to the .csproj files.
Jan 03, 2013 04:44 PM|LINK
Okay, so then you do not need to put the project files into your production environment. Look into the publishing features in Visual Studio 2010 so as to avoid putting any unnecessary files into production.
Jan 03, 2013 04:49 PM|LINK
Where are the "publishing features" located in VS 2010?
Jan 03, 2013 09:40 PM|LINK
In the Solution Explorer, right-click on the solution and you should see an option for publishing.
Read more about deployment strategies here: