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

Cake.Net creates a tools folder at the root which contains downloaded packages and should not be checked in.

.jfm files have started blocking checking for .sqlproj projects in Visual Studio. .jfm files are a new file-type created by the Microsoft ESENT database engine - this is a recent improvement only in Windows 10 Anniversary update. As the SSDT .sqlproj type in Visual Studio uses this engine for .dbmdl metadata files, and this file is locked by the user, this currently blocks users from checking into Git repositories.

This fix helps mitigate this by avoiding checkin of this file type.

__pycache__/
*.pyc

I've just upgraded to ASP.NET Core RC2, and I've found that Visual
Studio is producing a file called project.fragment.lock.json. When I
delete the file it is recreated during build. Given project.lock.json is
already ignored this looks like another file to ignore.

Commit a25589c9 introduced an ignore line for ApplicationInsights.config. This change breaks builds on certain systems, namely VSTS.

The current ASP.NET 4 template adds ApplicationInsights.config to the project's .csproj file. When VSTS attempts to build the project, it will fail if it cannot find ApplicationInsights.config.

ApplicationInsights.config is a required application file and should not be ignored.

https://www.google.com/?gws_rd=ssl#q=_pkginfo.txt&nfpr=1

I found I have this file not being ignored and a quick search shows these files :/

Added bower_components to .gitignore

Windows Azure -> Microsoft Azure. Due to https://azure.microsoft.com/sv-se/blog/upcoming-name-change-for-windows-azure/

Ignore Azure ApplicationInsights.config in VisualStudio.gitignore

The authoring of NuGet packages quite often include `build` folders, and when this is .gitignore'd it's very often the source of bugs in files that don't get checked in.

I've never seen a Visual Studio project that builds to a `build` folder (`bin` is the default name). As this is a Visual Studio template file, and we have real projects that include `build` folders that include source code, I recommend we remove suppression of this folder.

StyleCop.Analyzers is the modern re-invention of StyleCop, and uses a StyleCop.json file that the default .gitignore file made very difficult to check in, and easy to think was checked in but isn't.
See https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/32057fff82adf7cfb92aa50aef69a6b030eedf31/documentation/Configuration.md#source-control for the documented case.

Looking through history, this line was last touched to make it case insensitive, and before that the line was in the original VisualStudio.gitignore file, without justification for why it should ignore all file extensions. From my experience with stylecop, the only file I remember it creating was stylecop.cache. I would change `[Ss]tyle[Cc]op.*` to `[Ss]tyle[Cc]op.cache` but there is already a line for suppressing all *.cache files (which wasn't there when the stylecop line was originally added). So I believe this line is now obsolete, and as I explain above, actually problematic.

Added extensions of new database engine for C++ (sqlite-based) from
Visual Studio 2015
(Tools - Options - Text Editor - C/C++ - Experimental - Enable New
Database Engine)