We have a master solution that has all 500 projects in it in a directory that the build uses. The folder of solutions/projects is sampled below.
Solution1.sln
\ProjectA\Project1.vbproj
\ProjectB\Project2.vbproj
Starting with VS 2013 (Update 2), if a developer opens Project1.vbproj, Visual Studio now seems to open the Solution1.sln (and all 500 projects) which is not required and very slow for our developers. VS 2013 (RTM) and VS 2013 (Update 1) did no behave this way. Is this a bug or is there a way to disable this in VS 2013 Update 2.
Thanks
Scott
Related
I have two versions of Visual Studio running side by side (2019 and 2022).
When I open VS 2019, I see that it is connected to TeamExplorer and has a workspace associated with the install.
When I open VS 2022, I don't see that workspace, although I am on the same computer.
How can I work with the same projects that I have already downloade from Team Explorer in Vs 2022 and also check-in the code from VS 2022?
I can edit the code in VS 2022, but each time I have to check it in, I have to save the file, open VS 2019 and then check-in the project.
I want the option to check-in from either version of Visual Studio as the files are getting checked in the same repository.
Edit: Yes the VS 2022 is connected to the Visual Studio Online TFS.
I installed Visual Studio 2015 Enterprise Version 14.0.24720.00 Update 1 and wanted to create "Report Server Project". However it was not available. I tried to google the solution and most were saying to go to:
TOOLS > EXTENSIONS and UPDATES > UPDATES and check for updates related to SSDT and update it. I tried updating it but it is
not continue updating. For others it worked, but for me it didn't.
So ALTERNATIVE SOLUTION is to download SSDT from : SSDT for Visual Studio (VS) 2015.
Choose the appropriate language you need to download.
SSDT for Visual Studio 2015 SCREENSHOT
Here is the direct link for Visual Studio 2015 English: Visual Studio 2015 English
After installing, Report Server Project Template will now appear in NEW > PROJECT:
Report Server Project Template is now available SCREENSHOT
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.
We have MS Reporting Services .sln files that we open with Visual Studio 2005. We are moving to Visual Studio 2015. When trying to open the .sln files with Visual Studio 2015 we get the following:
We choose to upgrade and get the upgrade report that reports it was successful:
However when trying to open the .sln file after the successful upgrade was reported, it cannot open it.
Any ideas how I can get these files onto the latest version?
Reporting Services is not available in Visual Studio 2015 SSDT yet - it is still in Beta, as noted here hence your issues.
I am trying to build fltk 1.1.10 in Visual Studio 2013 but I get the warning
"fltk.sln: Visual Studio needs to make non-functional changes to this project in order to enable the project to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without impacting project behavior."
After searching, I found out how to do this for a C# project but how can I do it for fltk.sln?
Many thanks for the help.
There are 3 solutions in the FLTK1.1.10 distribution
visualc - for Visual Studio 6
vcnet - for Visual Studio 2003
vc2005 - for Visual Studio 2005
None of these will load directly into VS2013. They have to be converted to VS2013 format. Easiest way is to make a copy of vc2005 and call it vc2013. Then start fltk.sln. It will tell you that it needs to make a one way upgrade with the message you described. Just click OK.
What this does is migrate the 2005 sln to 2013 sln and migrate the vcproj files to vcxproj files. Basically you don't lose the vcproj files - you just get completely new versions of vcxproj files. Once that is done, just do a build.