I've been using VS 2015 with no issues. I upgraded to Visual Studio 2017, but I'm having this issue:
I have "Automatic brace completion" enabled. However when I select a Method in intellisense, it does not include parenthesis. How can I fix this? I've tried resetting my settings to default, too.
Related
There is a lot of answers related to upgrading a solution from Visual Studio 2017 to Visual Studio 2019 on StackOverflow. But how do I downgrade back to Visual Studio 2017? When I try to build a project in Visual Studio 2017 I get the following error:
Error MSB8020.
The build tools for v142 (Platform Toolset = 'v142') cannot be found. To build using the v142 build tools, please install v142 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the Project menu or right-click the solution, and then selecting "Retarget solution".
Before that, I used Visual Studio 2019 with the solution and it worked fine. But now I have to use Visual Studio 2017 instead and as expected I have errors. Is there a way to fix it not recreating the solution manually? Thanks for advice!
This problem is with your MSBuilder, re check the version of MSBulder in Visual Studion sometime it may be still support for vs2019.
or
You can changed this in your project
to: Project->Properties->General->Platform Tool_set and change to the current version of your VS.
Think this will be helpful.!
I inherited a project that was created in Visual Studio 2015 with SQL Server Data Tools version 14.
I'm running VS 2017 version 15.6.0 with SQL Server Data Tools 15.1.61801.210
When I try to open the solution it just fails with the below error message. What do I need to do in order to "upgrade" the solution so I can work with it?
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- LabSOR, "C:\Users\GROSCH\Documents\LabSOR\ETL\LabSOR_SSIS\LabSOR\LabSOR.dtproj"
No changes required
These projects can be opened in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1 without changing them.
- LabSOR, "C:\Users\GROSCH\Documents\LabSOR\ETL\LabSOR_SSIS\LabSOR.sln"
Ended up the SSDT integration elements hadn't installed. Once I did that I could right-click on the project in the solution explorer and reload it, and then it started working.
I recently updated my Visual Studio 2017 from 15.4.2 to 15.4.5.
At some point during the day I realized that in debug mode I could no longer view objects while stepping through code. I brought up VS 2015 and that environment still works.
Some things I found online suggested setting certain values in the debug options menu on the visual studtio environment, but that did not help either.
The Image shows there is no expand arrow to view the SomeObject item.
(visual studio 2017 bug)
This image shows my same machine with Visual Studio 2015 and the expected behavior. Until recently 2017 had this behavior.
(visual studio 2015 expected behavior)
I just test it in VS 2017 15.4.4 and 15.5.0. They all could show all items' value.
Since the latest VS 2017 has been updated to 15.5.0, if possible, please try to use the latest version. Debug it again.
I have C++ VS2008 project and my lovely IDE VS13. How can I work into VS13, but compile and debug project like in would be VS08. When I open VS2008 *.sln files that wrote to me about one-way upgrade, and how you i guess you understand, project after open in vs2013 don't open in vs2008.
For now, I use VS13 like notepad then copy all files text to alt+tab opening VS 2008 IDE and there are run project. And again work in VS13.
Based on Microsoft product lifecycle policies,
https://support.microsoft.com/en-us/lifecycle/search?sort=PN&alpha=Visual%20Studio&wa=wsignin1.0
Visual Studio 2008's mainstream support ended in April 2013, while Visual Studio 2013 was released in Jan 2014. That means Visual Studio 2013 will not support Visual Studio 2008 bits, so not a surprise if native multi targeting does not show v80.
I don't think you can easily get side by side, as VS2008 is too old, and its C++ project is not even MSBuild script. Once converted to VS2013, there is no way back.
Why cannot you just let VS2008 go? I guess that's why you get so many down votes.
You can't convert the solution to Visual Studio 2013 and still open it in Visual Studio 2008. You can, however, tell Visual Studio 2013 to use the Visual Studio 2008 compiler.
To do that, convert your solution to Visual Studio 2013 (don't forget to keep a copy of the original file, just in case), then open the project properties, go to the General options and select the Visual Studio 2008 platform toolset.
I have a VS 2012 project that worked fine till the template issues in c++ started causing problems in VS 2013.
Some one mentioned changing the compiler to VS 2012 in the settings will fix the issue by using the same compiler the VS 2012.
Steps to do this i was told was to first install VS 2012 then change the setting in the project properties.
How there does not seem to be a setting to change the compiler.
How do I change the compiler in VS 2013 to VS 2012?
=============== EDIT ===============
herohuyongtao below explained the compiler change Thx
However despite installing VS2012. VS2013 properties does not see VS2012 when i hard code the value 110 it says "Visual Studio 2012 (v110) (Not Installed)"
any thoughts on how to resolve that?
=============== EDIT ===============
The version of VS 2012 is express which is registered now. Will this work with VS 2013 pro?
=============== EDIT ===============
Also just installed Microsoft Visual Studio Tools for Applications 2012
http://www.microsoft.com/en-gb/download/details.aspx?id=38807
as recommend by the compiler error when tried to compile with v110 even though it was not there
Right-click the project in Solution Explorer and select Properties, and then:
Configuration Properties > General > Platform Toolset > v110.