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
Related
As mentioned yesterday, I'm having some issues with my debugger (sometimes it shows wrong values).
This morning I almost exploded on this particular case:
I was interested in information about the DB, used by my application, so I put a breakpoint on a line, where the corresponding object is used. As the debugger said that particular object is null, I was extremely surprised being capable to the following line, as you can see in the screenshot.
For me, this is the clearest proof that my debugger is so bogus and I would like to update it, but I don't know how. My current visual studio about mentions the following:
In text format:
Microsoft Visual Studio Enterprise 2017
Version 15.9.44
VisualStudio.15.Release/15.9.44+28307.1800
Microsoft .NET Framework
Version 4.8.04084
Installed Version: Enterprise
Microsoft Visual Studio Tools for Applications 2017 00370-00007-85954-AA413
Microsoft Visual Studio Tools for Applications 2017
Is there a known issue for this particular visual studio version, .Net framework version, Telerik version, ...?
Version 15.9.44 is, as of today, the latest available build for VS2017. You should consider upgrading to VS2022. To upgrade, just download the latest visual studio installer from microsoft (https://microsoft.com/vstudio). It lets you select the version to install. You can install VS2017, VS2019 and VS2022 in parallel (given enough free disk space).
[I asked this question in MSDN in June and have had no replies as yet so I am hoping that I can get an answer here. A stackoverflow search for "uwp blend" yielded exactly 100 results, none of which are for the same issue as here.]
I created a brand new WIndows Template Studio solution - called "AppName" - with VS 15.7.3 and added a .NET Standard 2.0 class library project - called "ConversionService" - to the solution.
When I tried to open the solution in VS Blend 15.7.3 (same version number as VS) I got the following - rather scary - message:
One-way upgrade
Visual Studio will automatically make functional changes to the following projects in order to open them. You will not be able to open these projects in the version of Visual Studio in which they were originally created.
- ConversionService, "[location redacted]ConversionService.csproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
- AppName, "[location redacted]\AppName.sln"
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.
- , ""
What does the above message mean? (I redacted the actual file locations.)
It seems to say that I won't be able to go back into VS to edit the ConversionService project, which is definitely something I want to be able to do.
Why does VS Blend 15.7.3 seemingly not like projects created in VS 15.7.3?
(I previously had the same issue with another completely separate solution containing UWP and NET Standard projects but I didn't need Blend for that.)
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.
I have visual studio 2015 and InstallShield LE.
Everything was fine and suddenly I get "Incompatible" problem. "The application is not installed".
I was trying to reinstall the installsheild and it didnt help.
when i do right click on the project i click on "Reload project" and get this message:
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.
- Setup, "C:...\Visual Studio 2015\Projects\TestProject\Setup\Setup.isproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2015, Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
Probably not what you want to hear, but do yourself a favour and uninstall it as fast as possible! It's an awful piece of software, full of bugs, pathetic or non-existent support, and a steep price if you are dumb enough to want to buy it!
This is the voice of bitter experience, backed up the opinions of a lot of other people who found the same thing.
I use Inno Setup, which is free, simple, is supported and works really nicely. Since discovering it, I've not had any problems.
Can other version of Microsoft Visual Studio be opened with Microsoft Visual Studio 2005 C#?
Projects created with previous versions can, and will invoke a project conversion wizard. Projects created with later versions cannot, generally. I found a downgrade utility on, of all places, Mises.org. I didn't write it, and haven't even tried it, so your mileage may vary.
You can open projects created with older releases of Visual Studio 2005, like 2002. A migration assistent will help you to update the project files.
If you're asking if you can run, say, an instance of Visual Studio 2008 next to 2005, then yes. I've done it many times. When you double-click on a .sln file, what actually runs is a little stub program that examines the .sln and decides which is the best version of Visual Studio to launch it in.
If you're asking whether you can open a solution created in VS 2005 in another version of VS, then the only restriction is that it has to be more recent than VS 2005. EG: you can't open a Visual Studio 2008 solution in VS 2005.
Sometimes you can change the version of the solution file manualy. Open it in text editor and manually change the line "Microsoft Visual Studio Solution File, Format Version 11.00" to earlier. Sometimes can help :).