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.
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.
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).
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.
* 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
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.
- 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
Kevin R. RaneyandGitHub
AndrewandGitHub
Jeff CyrandGitHub
Matthias Schäfer
ofthelitandGitHub
John Vandenberg
Giovanni BassiandGitHub
Nick SchonningandGitHub
Matthew RobbinsandGitHub
linluxandGitHub
Brendan ForsterandGitHub
Quique Fdez GuerraandGitHub
komaflash // ec8orandGitHub
raterusandGitHub
jerzywie
tobyandBrendan Forster
Enrico SadaandBrendan Forster
Tuomas-Matti SoikkeliandBrendan Forster
Denis PeshkovandBrendan Forster
Aayush KapoorandGitHub
Noctis-andGitHub
Dean Butcher
synepisandGitHub
jimbob7198andGitHub
CodeNotFoundandGitHub
James KoandGitHub
Yann Duran
Amadeusz Wieczorek
julienshepherdandGitHub
JP DillinghamandGitHub
Matt SmithandGitHub
Robin Hultman
MichaelKogan
Victor UriarteandGitHub
Brendan ForsterandGitHub
Gary Ewan ParkandGitHub
Jules BlokandGitHub
Henrik W. MoeandGitHub
ChuckLu
Jørn Christensen
mrs-mrlandGitHub