After upgrading from Visual Studio 2013 web site projects to Visual Studio 2015 web site projects (NOT web application projects), every time the project builds it checks out the solution file and a diff doesn't show any changes to the solution file.
We are also running ReSharper Ultimate 10.0.1. The Visual Studio edition is the enterprise, if that makes any difference.
I had the same issue. Deleting the hidden folder ".vs" in the same directory as the solution file fixed the issue.
Related
I am upgrading my project from visual studio 2010 to visual studio 2015
please tell me is there any need to upgraded the ms-build project.
Follow these steps to upgrade project created in earlier versions of VS this may help you:
In VS, on the File menu, click Open and then click Project/Solution,
Web Site, or File, depending on the kind of project you are
upgrading.
In the Open Project dialog box, select a project file, and then click
Open. If VS detects that the project or file was created in an earlier version of Visual Studio, the Visual Studio Conversion Wizard opens.
Complete the Visual Studio Conversion Wizard.
Refrence
is there any need to upgraded the ms-build project?
The answer is No. That because since start with Visual Studio 2013, Visual Studio team made a number of exciting changes to MSBuild for Visual Studio 2013. Now the 2013 version of MSBuild will ship as a part of Visual Studio instead of the .NET Framework. See this blog MSBuild is now part of Visual Studio! for more detail info.
You can find the MSBuild.exe from the directory: C:\Program Files (x86)\MSBuild\14.0\Bin
Since it ships as a part of Visual Studio 2013, just as Michael said, MSBuild upgrade should happen with the VS installation. So you do not need to upgrade the MSBuild separately.
Hope this helps.
Is there any way that I can use the latest IDE (VS2015) to work with my old solution project but i don't wish to upgrade my project?
Unfortunately, you cannot do this. The format of project and solution files was changed in VS 2010, so the furthest back you could possibly go with VS 2015 would be to VS 2010.* And that wouldn't help you any for cross-compatibility, since VS 2008 can't open VS 2010 project files.
You have no real choice but to allow the IDE to convert your solution and project files to the latest version. However, this will not delete your old VS 2008 project/solution files. They will still be in the solution directory, and will still work for opening the solution in VS 2008. The new project/solution files will open the solution in VS 2015.
This was a very common strategy employed by open-source projects before recent versions of Visual Studio implemented cross-compatibility. They would just have multiple versions of project and solution files for each supported version of Visual Studio.
The only disadvantage with this is that changes you make to one version of a project or solution file don't propagate to the others automatically. But this isn't really that big of a deal, since once a project is reasonably mature, the project and solution files don't change very often.
* In fact, VS 2015 interoperates smoothly with project/solution files from VS 2013, VS 2012, and VS 2010 SP1. It can create and modify project files for any of these versions. See MSDN: Porting, Migrating, and Upgrading Visual Studio Projects (for Visual Studio 2015)
I am trying to open the Direct3D Tutorial Win32 Samples with VS 2013 Express for Windows Desktop. To my surprise it claims that the individuals projects in the solution each cannot be opened because their project types (.vcxproj) are not supported by this version of the application.
Does anyone know why the vcxproj files cannot be opened, or how I could diagnose and repair the root cause of the problem?
Edit: I can also not open the vcxproj files in Mike Farnsworth's Rayito project.
It means that the projects were created in another version of Visual Studio.
Try to upgrade the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting Upgrade Solution.
Alternatively you could use Visual Studio 2012 Express Edition to see if that resolves the problem.
Windows Dev Center indicates that Visual Studio 2012 is required.
Hope this helps
Neither of the other answers seemed to help.
I uninstalled visual studio. I uninstalled SQL server. I reinstalled visual studio. Now it loads C++ projects correctly.
I understand a previous install of visual studio can cause the problem I was having. Apparently so can installing SQL server Express prior to installing Visual Studio 2013 Express.
Yesterday I have installed Visual Studio 2012 Premium on my SharePoint 2013 Development Machine. I also installed the Office Developer Tools to get the SP2013 Project templates.
Opening my SP 2010 Solution File and converting to 2013 was successful.
My problem: There is no "Deploy"-Button in the Project-Context-Menu anymore. Everything is there: Build, Rebuild, Retract etc.
But no Deploy.
Asked this in the SharePoint Forum too
I had the same problem.
I started by creating some solutions folders, and placing my SharePoint project in those. After moving a project from root --> frontend\ , the deploy menu item, in the context menu of the project disappeared.
I solved this, I had to move the SharePoint project to the root-folder of the solution, and the deployment feature re-appeared in the project context menu.
I've inherited a SharePoint 2010 project that was originally created in another environment using a different version of Visual Studio (2012). My issue is that the .g.cs files for some WebParts are not being [re-]generated when I make changes to the .ascx files. I know that for regular .aspx pages, you can right-click and choose "Convert to Web Application" to force generation of the designer files. Is there something similar for WebParts?
I've already tried deleting the bin\ and obj\ directories in the project, cleaning and rebuilding (both the solution and the project), as well as trying to re-create the WebPart from scratch.
Wrote about workaround here: http://sadomovalex.blogspot.com/2013/08/fix-bug-in-visual-studio-2012-with.html. You need to specify url of correct Sharepoint site on local dev environment in "Site URL" property of your project.
It seems that it's an issue from going between Visual Studio 2010 and 2012. On the 2012 box the .g.cs files are regenerated and updated fine but the 2010 box refuses to do so.
Correction: SharePointWebPartCodeGenerator wasn't being found. After re-installing the Visual Studio 2010 SharePoint Power Tools, the .g.cs files were being updated.
I searched forever for a fix and installing the 2010 SharePoint Power Tools solution fixed the issue! The solution I was working on must have been a 2012 Sandbox solution.