This is to ignore the new Nuget Symbol Packages, which are now the recommended approach for debug symbols of public NuGet packages.
https://docs.microsoft.com/en-us/nuget/create-packages/symbol-packages-snupkg

ASP.NET Core projects no longer use Bower by default (since Bower is now deprecated), and instead create static files in the wwwroot/lib path.  This path is can also be used by convention for ASP.NET Core developers, and since it's no longer populated by Bower, it is unituitive to be excluded by default.

This change removes the lines added by #2307.

**Reasons for making this change:**

VS default flow is now broken by excluding files required to run an ASP.NET Core project.

**Links to documentation supporting these rule changes:**

The changes to the ASP.NET Core templates was tracked by https://github.com/aspnet/templating/issues/48.

Visual Studio can also generate .appxbundle and .appxupload files for Windows Store apps.
See: https://docs.microsoft.com/en-us/windows/uwp/packaging/packaging-uwp-apps#types-of-app-packages

* Update VisualStudio.gitignore file

Rider has its own ignore file, so does Visual Studio. The ignore statements for Rider (idea) IDE should be removed from Visual Studio .gitignore file template.

Ignore backup files from editing reports

Ignore liveness db which belongs to:
https://github.com/Xabaril/BeatPulse

This will ignore SQL Server Reporting Services user files

Currently, CodeRush provides the capability to store team settings and images used in Rich Comments and they should be shared among all team members. I have corrected the gitignore file to exclude only personal settings.

_i.h given in 799ee6b7#gitext://gotocommit/799ee6b79e1d32f49ded6683b5364017fd4ee0a5 is wrong

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