https://github.com/github/gitignore/commit/08def965cd1c0241a7cffbe7c26a74b3cab61243 incorrect states that commenting *.pubxml will keep your passwords hidden when it will actually do the opposite. This clarifies what commenting *.pubxml does and warns you of the dangers.

Amends #1131
See these resources for explanation:
  http://docs.nuget.org/docs/reference/package-restore
  http://docs.nuget.org/docs/workflows/using-nuget-without-committing-packages

Removed the separate top-level patterns for NuGet in accordance with comments in PR. Will now match version 2.0.1.

Fixed pattern for excluding nuget packages so that it works both for top level package folder and for any lower level package folders.  Re-include patterns fixed the same way.

When installing SQLite embebed on my C# project I've noted that it generates both directories,
`x86` and `x64` but only `x64` was present on `.gitignore`.

Building NuGet packages locally with `NuGet.exe pack <name>.nuspec` generates a `<name>.<version>.nupkg` file which should never be versioned.

"Releases" directory is created by Shimmer/Squirrel installer for example. It also should be ignored.

Without the asterisk at the end of the directory's path, an exception for
a file within this directory does not work.
(ex. !packages/repositories.config)

This reverts commit 0fb0fbef.

This was ignoring .ncrunchproject and .ncrunchsolution files.
NCrunch recommend that both of these files are checked in to source control.

Submitting this for consideration.

The first thing that I do on every new project is to go in and uncomment the packages folder. With the prevalence of NuGet and prominence of its use in the Visual Studio environment, along with how well package restore *just works* now, I believe this should be the default.

While I understand that package restore isn't on by default, I would argue that the types of developers using NuGet _and_ a distributed SCM are the types of developers that would omit the binaries from source control.

This commit Makes VisualStudio.gitignore ignore the three items below. It needs when you create an ATL Project.

* [Dd]ebugPS/
* [Rr]eleasePS/
* dlldata.c

web deploy settings include unencrypted passwords

I have no idea what this is doing here, totally unrelated to Visual Studio. There is a special OSX gitignore file that you can use.

* Ignore Azure publish *.azurePubxml files
* Add a trailing slash to csx
* Remove random whitespace after build output

Ignores generated Fakes assemblies and related files placed under the FakesAssemblies directory.
These files are generated at build time from the *.fakes configuration files.

WCF tracing files (.svclog) are used by the Service Trace Viewer Tool.

Files ending in .dbproj.schemaview contain state persistence settings
for the Schema View utility within Visual Studio.

http://stackoverflow.com/questions/3937160/in-the-new-visual-studio-2010-sql-server-project-type-what-is-the-dbproj-schem
http://foocompelsyou.wordpress.com/2012/05/06/visual-studio-2010-database-projects-why-use-them/

Ignores the compiled typescript files that chutzpah creates. Alot of files are created, so ignoring them have an high impact on repository health.

Some tools like TeamCity depend on repositories.config being checked-in under `packages/` for the restore to work.

Added DebugPublic of Matrox DSK