Local History for Visual Studio automatically creates a history of your files every time they are saved. The history can be compared with the current version. It is a solution situated between version control and undo/redo of history, available by default in Eclipse and IntelliJ IDEs.
https://marketplace.visualstudio.com/items?itemName=AronDCurzon.LocalHistoryforVisualStudio
https://marketplace.visualstudio.com/items?itemName=lostalloy.LocalHistory-for-Visual-Studio

Ignoring `launchSettings.json` does not make much sense. Now .NET CLI even considers this file when running with `dotnet run`, as you can read [here](https://docs.microsoft.com/en-us/dotnet/core/tools/dotnet-run?tabs=netcore2x).

This settings will be useful if shared among project members, so it should be commited to the repo.

Also, on the default `.gitignore` file generated by Visual Studio it is not ignored, so this causes confusion, as depending on how `.gitignore` was created it could be commited in or not.

The conversion process from the old custom rptproj to the MSBuild based projects creates a .bak backup file

MFractor is a Xamarin/Visual Studio Mac productivity tool used by 1000's of Xamarin developers.

The `.mfractor/` folder should not be included in source control (but often is).

"These files are produced when Incremental Link-Time Code Generation (LTCG) is enabled."
https://stackoverflow.com/questions/31554559/possible-to-stop-generating-ipdb-iobj-files-by-visual-studio-2015

Nobody is using v1 of typings anymore on new projects and 'typings' is the recommended name for the folders of your custom types.
On the other hand the official Visual Studio ignore is not ignoring this folder.

The latest update of Visual Studio 17 (15.5.5) introduces a new backup folder called "ServiceFabricBackup" before upgrading service fabric applications.

The VS 2017 version of the Business Intelligence project contains a user file (*.rptproj.rptuser) that should be ignored as well

* Add *.snk strong name key files

Strong name key files shouldn't be included in a repository AFAIK. they are intended to sign build output to verify that it comes from the correct publisher. having an *.snk in a repository would allow anyone to produce build as if they were the original publisher.

I guess some OSS projects might like to have *.snk files in their repos but that would be an exception to the rule.

* Make use of *.snk optional

Add note explaining use.

* Reduce explanation

Just use a link instead

ref http://msbuildlog.com/

* Update VisualStudio.gitignore

It looks like VS2017 changed it's nuget package directory name to be capitalized.
When using Ubuntu for Windows, directory name casing of NuGet package folder becomes important and detected as a change by git,. This change is to ignore regardless of casing.

AxoCover is a Code Coverage Tool. It creates a **.axoCover** folder where are created:
- settings in settings.json
- sub-folders into **run** folder which contain code coverage results.

All content into **.axoCover** folder must be ignored except the **settings.json** file.

for .appx files created in the project root directory.

Secondary data files .ndf (https://msdn.microsoft.com/en-us/library/ms189563.aspx)

- It is recommended to include the packages.config file when using Cake
- This ensures that the Cake version that is being used is *pinned* and updated only when the user decides

If the .gitignore file is inlcuded in another project, it may be feasible to have a reference to origin.

Reference: http://stackoverflow.com/questions/1826901/should-i-add-vcxproj-filter-files-to-source-control

see e.g.
http://stackoverflow.com/a/1530193
https://msdn.microsoft.com/en-us/library/aa241721(v=vs.60).aspx