The security update addresses the vulnerability by correcting how NuGet restore creates file permissions for all files extracted to the client machine. Details about the packages can be found in the.NET Core release notes. Visual Studio 2017 version 15.9.7 Service Release- released on February 12, 2019. Installed the Visual Studio Build Tools with VS 2017, VS solutions cannot open by double click and it seems the VS version selector is broken. Fixed in: visual studio 2017 version 15.7 preview 3 solution windows 6.1 visual studio 2017 version 15.5 Setup Fixed In: Visual Studio 2017 version 15.7. Information about Microsoft Visual Studio Version Selector. Microsoft Visual Studio Version Selector is mostly used to open: Programming files by 56% of users; Microsoft Visual Studio Version Selector is usually found in following folders:%ProgramFiles% (x86) Common Files Microsoft Shared MSEnv VSLauncher.exe. The VSLauncher.exe is a Microsoft Visual Studio Version Selector. This file is part of Microsoft® Visual Studio® 2010. VSLauncher.exe is developed by Microsoft Corporation. VSLauncher.exe is usually located in the%PROGRAMFILESCOMMON% sub-folder and its usual size is 258,384 bytes. Indeed, the free version is Visual Studio Community Edition, and you can use it even for commercial products as an individual or small team (for the exact terms and conditions, see the Microsoft's site). Visual Studio IDE Microsoft Visual Studio.
Active3 years, 1 month ago
Trying to open a VS 2012 solution (SLN file) explicitly in VS 2013 succeeds. Simply double-clicking it in Windows Explorer still opens it in VS 2012 instead.
I've read 'Visual Studio 2012 doesn't convert vs2010 solution?' and followed the suggestion to 'Save As..' the solution file.
Still it opens in VS 2012 by default.
My question:
Pogo poppit free full screen. How to change a SLN file to force it being opened in Visual Studio 2013?
Community♦
Visual Studio Version Selector DefaultUwe KeimUwe Keim
28.4k3333 gold badges142142 silver badges229229 bronze badges
6 Answers
The
.sln file indicates the intended version as one of the early lines - for example:
or:
However - it can only make use of this if the default application for
.sln files is the 'Microsoft Visual Studio Version Selector'. It is not uncommon for the default .sln application to be a specific version instead. In windows 8:
you can tell which is the default because it says 'keep using':
Marc Gravell♦Marc Gravell
825k213213 gold badges22282228 silver badges26242624 bronze badges
Note that you can also force the upgrade of a .sln or .proj file by using the commandline, where devenv is the target IDE version:
Example:
![]()
Note that this does not open Visual Studio. An alternative is to, from within the IDE, select 'Save As' for your solution file and overwrite or save the solution under new name.
Read more:http://msdn.microsoft.com/en-us/library/w15a82ay.aspx
zumeyzumey
Seems like the OP has a working answer already .. but for me the problem was different. I had a VS 2012 solution (several actually) and wanted to convert them to 2013 (which I understand is a trivial change to the .sln file, but I wanted it done automatically in case there was some secret upgrade logic I was unaware of).
So I thought I would open it in VS2013, it would automatically upgrade as expected, and then I'd be set to double click the solution and see it in VS2013 going forward. But opening in VS2013 was NOT upgrading the solution for me automatically as expected and I could not find an explicit way to force the upgrade after opening the file in VS2013. I could work with the solution, save my changes, and close VS2013, but the .sln would remain unchanged and un-upgraded.
Turns out my problem was in how I was opening the solution .. as a habit I right click files and select 'open with' to choose the program I want to use to open a file. I do this frequently. Note I am NOT talking about changing the default 'open with' program but just opening a file with a specific program once. So I would right click the .sln file.. open with Visual Studio 2013 .. Best free sniper shooting games for android. and nothing would upgrade.
Eventually I thought to go into VS2013, then do File > Open and select the .sln file (this is foreign to me since I hardly if ever open anything this way, maybe you are the same way). Anyway that did upgrade the solution file instantly.
After upgrading, lines 2-3 of the .sln file changed from this:
to this:
So from my experience, to automatically update a VS2012 .sln to VS2013, you must open VS2013 and select the .sln from the File > Open dialog. Using the explorer shell to force the .sln file to open in VS2013 does not invoke the upgrade logic (apparently).
As a further note, I tested with another solution, and after making changes through Configuration Manager (which obviously 'touches' the .sln file) it did upgrade a VS2012 to VS2013, even after having opened it through right-click open with.
TCCTCC
2,10411 gold badge1818 silver badges3434 bronze badges
I had a solution that had previously been upgraded from 2010 to 2013 successfully but still showed the .sln as associated with 2010.
I tested all the methods given in this thread and the only one that successfully corrected the .sln was to open Visual Studio 2013 alone, then open the solution that still was associated with 2010 in the IDE, then use the [File] > [Save (name).sln as] to overwrite the existing .sln file.
Setting the file assoc of the .sln to be the 'Visual Studio version selector' made no change and the solution continued to open in 2010.
The devenv (name).sln /upgrade method made no change to my .sln file.
Hacking the raw text of the .sln file corrupted mine and it would not open at all.
JeffJeff
To solve this issue I just changed the following lines of the .sln file:
into these:
The comment line is to be changed as it is parsed by the solution loader.
ZacZac
3,56733 gold badges3030 silver badges3939 bronze badges
This may work for readers attempting to upgrade a solution file to Visual Studio 2015. (I upgraded a VS 2012 solution.)
You may want to delete the removed project folder at this time since step 3 did not delete it.
This worked for me when neither zumey’s nor TCC’s answers did.
EDIT
Metro Smurf had a similar, but easier answer than mine for a similar question. His steps were:
![]()
Community♦
TheophilusTheophilus
Not the answer you're looking for? Browse other questions tagged .netvisual-studio-2012solutionvisual-studio-2013 or ask your own question.Comments are closed.
|