We Keep Coding

Unsupported python project in Visual Studio 2017

I had a VS2015 solution with a C# and python project in it. Now I upgraded visual studio to "2017 community preview" version.
If I try to open the solution from Visual Studio by clicking on File/Open/Project... it pops up the following error message:
Unsupported. After that VS cannot open the python project in the solution (it sais "incompatible" next to the project file). It can open the C# projects.
But if I simply double-click on the *.sln file, VS automatically starts up and offers the following one-way upgrade: One-way upgrade. After doing the upgrade it can open the python project as well and everything works properly.
Even though after making the one-way upgrade the first type of opening (from VS) still does not work. Opening by clicking on the solution file still works.
Thanks for any help how I can resolve this issue.

Python tools for visual studio 2017 is only available for the preview version. It will be added soon to the non-preview version.
source: https://blogs.msdn.microsoft.com/pythonengineering/2017/03/07/python-support-in-vs2017/

OMG, I got the answer...
I had both VS 2017 community and VS 2017 community preview installed on my computer. (That is because obvously I installed the simple community version at first, and only installed the other when I realized it does not support python.) I did not either think that preview version will not overwrite the existing one but will make a new install.
So when I click on the sln file it opens up with the preview version of VS, but the shortcut in my start menu refers to the normal version... :S :D

No Colours in Specflow Feature Files on Visual Studio

I have the latest version of SpecFlow installed, and still the feature files display uncoloured, like so...
(Not enough rep to insert images)
Specflow uncoloured feature files
Is there certain configurations that are set for colours to be displayed in Specflow files?
VS2015
Specflow 2.1

There is an option for coloring syntax in Tools->Options->SpecFlow that could cause the problem.
EDIT:
Ensure your SpecFlow extension is installed correctly:
Go to Tools->Extensions and updates -> Installed look for SpecFlow for Visual Studio 2015. You might try to uninstall and install it again.
If you can't find in the list then select Online, in search type specflow, then select result and install.

Gherkin code highlighting issue on Visual Studio 2019
For Visual studio 2019 need to install an Extension
Extensions -> Manage Extensions -> Search for Specflow
Can see Extension by name 'Specflow for Visual Studio 2019' click and restart the Visual Studio 2019 app.

FIX for VS 2022
If this is still an issue, On update, the extension is removed.
Navigate to Extensions, Click Online, Search Specflow and install the extension.
Restart and modify
Fix is complete

In my case I had the coloring in some projects but in other I haven't. Pre-installing the Visual Studio extension worked for me.

GIT integration to show method history in Visual Studio

We use GitHub for our source code repository and Visual Studio for our development (C#). I downgraded from Visual Studio Professional (Trial) to Community Edition and somehow lost the GIT method history I had above each method signature. I've since reinstalled Pro version and still can't see it. This method history was very useful and looked something like:
Last Update 8/1/2015, 3 authors.
Void DoSomething() {}
Clicking on the status line would bring up things like "compare to previous version", history etc.
I'm not sure if it was a feature of Visual Studio Professional (doubtful) or one of the git extensions I possibly installed (see Tools->Extensions and Updates) or something else. I'm new to using GIT/GitHub, especially with Visual Studio and would appreciate some help. My specific questions
1. How do I get history/last author/etc for each method (not file)? Does it work under Professional and Community
2. What are some good Git Tools to install in Visual Studio to see changes/history, etc.? I'm using the command line to commit/push etc., but am not opposed to doing this from Visual Studio if it makes sense.
Thanks,
Dave

What you initially refer to is a feature of Visual Studio called CodeLens. It's available in the Professional and Enterprise editions of Visual Studio 2015, but not available in the Community edition.
To try and resolve this not working, I would:
Make sure you are actually running Visual Studio 2015 Professional edition, and not the Community edition.
Make sure you have Git for Windows installed.

In addition to the excellent answer by Steve (which I'm marking as answer), I'll note that I had additional problems (after installing Git for Windows).
I got errors at startup and didn't see the method info. The errors were:
The 'GitCollaborationPackage' package did not load correctly.
The 'FileIndicatorPackage' package did not load correctly.
The fix was to rename the componentmodelcache directory under C:\Users\cshar\AppData\Local\Microsoft\VisualStudio\14.0
See:
Packages not loading after installing visual studio 2015 RTM
or
http://kuebiko.blogspot.ru/2013/07/setsite-failed-for-package.html

No templates in Visual Studio 2017

After a Visual Studio 2017 (RC) installation from scratch, I can't find a standard list of templates. I'm specifically interested in the Console Application (C#) template and the Windows Form (C#) template. I'm pretty sure I'm missing one of the Individual Components. I'm not sure which one is supposed to be installed and I don't want to install all of them.
Please see my list with components installed.

You need to install it by launching the installer.
Click the "Workload" tab* in the upper-left, then check top right ".NET-Desktop Development" and hit install. Note it may modify your installation size (bottom-right), and you can install other Workloads, but you must install ".NET-Desktop Development" at least.
*as seen in comments below, users were not able to achieve the equivalent using the "Individual Components" tab.

If you have installed .NET desktop development and still you can't see the templates, then VS is probably getting the templates from your custom templates folder and not installed.
To fix that, copy the installed templates folder to custom.
This is your "installed" folder
C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\IDE\ProjectTemplates
This is your "custom" folder
C:\Users[your username]\Documents\Visual
Studio\2017\Templates\ProjectTemplates
Typically this happens when you are at the office and you are running VS as an administrator and visual studio is confused how to merge both of them and if you notice they don't have the same folder structure and folder names.. One is CSHARP and the other C#....
I didn't have the same problem when I installed VS 2017 community edition at home though. This happened when I installed visual studio 2017 "enterprise" edition.

I found the path and wrote it in the options

My personal experience was that I had installed the Team Foundation Server client for 2017 first (was using it as a Proof of Concept for our QA team, while I was still using VS2015), then followed it up with Installing Visual Studio 2017 later to begin development.
What I ended up with on my Start Menu was a Visual Studio 2017 and a Visual Studio 2017 (2). The Visual Studio 2017 (2) had all the templates I was missing. Following the steps found in the First answer to this question (which were clear and easy to follow) did not fix my issue. I had thought that launching the client would upgrade to the Development Client, but it did not. I renamed it to Visual Studio Professional, and now have everything I need. Not sure if this happens to anyone else, but it was what happened to me, so I hope this helps someone.

NOTE: this topic is about installation issues with MS project templates.
I came here via a search in Google, I was looking for a missing Template option in Visual Studio 2017 File menu: in VS-2015, it was Export to Template and I used it to add my own standard Project Items.
Meanwhile, I found an answer.. my issue was not related to default templates and it does not need install things. The option Export to Template has been moved to the VS-2017 Project menu !

I had to reinstall .NET desktop development (throught Workload tab), even button was showing: Modify
After that Visual C# selection appeared :)
(And now i can use Console APP Template)

In my case, I had all of the required features, but I had installed the Team Explorer version (accidentally used the wrong installer) before installing Professional.
When running the Team Explorer version, only the Blank Solution option was available.
The Team Explorer EXE was located in:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\TeamExplorer\Common7\IDE\devenv.exe"
Once I launched the correct EXE, Visual Studio started working as expected.
The Professional EXE was located in:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe"

My C++ templates were there all along, it was my C# ones that were missing.
Similar to CSharpie, after trying many modify/re-installs, oddly the following finally worked for me :
- run the installer, but un-select 'Desktop development with C++'.
- allow installer to complete
- run the installer again, and select 'Desktop development with C++'.
- allow installer to complete

In my case, I had all of the required features, but I had installed the Team Explorer version (accidentally used the wrong installer) before installing Professional.
When running the Team Explorer version, only the Blank Solution option was available.
The Team Explorer EXE was located in: "C:\Program Files (x86)\Microsoft Visual Studio\2017\TeamExplorer\Common7\IDE\devenv.exe"
Once I launched the correct EXE, Visual Studio started working as expected.
The Professional EXE was located in: "C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\devenv.exe"
This solved my issue, and the reason was I had enterprise edition previously installed and then uninstalled and installed the professional edition. Team Explorer was not modified later when I moved to professional from enterprise edition.

Visual Studio 2010 cannot open a 2010 solution that Visual Studio 2012 modified

Basically, I had a project that was written with Visual Studio 2010 Express in C#, I then tried out using Visual Studio 2012 Express with that file, and now VS2010 says:
"The selected file is a solution file, but was created by a newer version of this application and cannot be opened."
Now when I had looked up about this, Microsoft said that you can still use 2010 if you do not use anything that was VS2012 specific. Well, I had tried out the built in Testing that is in the VS2012, and that was the only thing that was VS2012 specific, but deleting that from my project (the Testing project), still left it saying that it was created by a newer version.
So, how do you make a VS2010 solution that VS2012 modified work with VS2010 again?

SP1 for VS 2010 is required to open VS 2012 modified solutions.

Try this out:
http://vsprojectconverter.codeplex.com/
Personally I've never used it but I have it marked as a tool to use if I run into issues. Hope it helps!

This probably isn't the kind of answer you are looking for, but it has worked for me in the past for compatibility issues and such, so it's worth mentioning. If your project isn't too complicated, you can create a new project then copy and paste everything across, starting with form controls, and then moving to the code. It's a sloppy solution that doesn't scale well, but sometimes nothing else seems to work.

The response here by Andrew.Wu is very comprehensive
http://social.msdn.microsoft.com/Forums/en-US/vssetup/thread/fc763995-beed-4287-97de-6e47d3e87865 and details steps to take to solve the problem

very old...but hope it can help someone...
Step 1: Go to your project location where the project's sln file is kept and then Right-click on it, choose "Properties". Uncheck "Read Only" as like given below:
Step 2: Again Go to the location where the project's sln file is kept and then Right-click on it to open it with notepad and change the "Microsoft Visual Studio Solution File, Format Version 12.00" to "Microsoft Visual Studio Solution File, Format Version 11.00" on the file.
you can change also the "Visual Studio 2012" to 2010