Doug Bunting c9f89dcc8b `msg` -> `message` ... - as discussed in https://github.com/aspnet/WebHooks/pull/210#discussion_r158419203 - `message` -> `queueMessage` where main change caused a conflict - also - `ack` -> `success` - `asm[s]` -> `assembly` / `assemblies` - `cnt` -> `i` except in 2 places where `count` was better - `count` -> `data` first in one of those cases - `combo` -> `combinedBytes` - `invalidFiltersMsg` -> `invalidFiltersMessage` - `se` -> `storageException` - leave `config` alone; exposed publicly e.g. `Microsoft.AspNet.WebHooks.Config.WebHooksConfig` nits: accept lots of VS suggestions - more `var` especially		2017-12-22 18:49:36 -08:00
..
DataSecurityTests.cs	Updated references to ASP.NET Core to RC2. ASP.NET Core is used as part of the Data Protection model for persisting WebHook registrations. The out-of-the-box IWebHookStore implementations for SQL and Azure Table Storage both use encryption when storing the registrations. Using the ASP.NET Core Data Protection module has explicitly been designed to facilitate data encryption and supports automatic key-rollover etc.	2016-06-05 09:11:27 -07:00
EmbeddedResource.cs	`msg` -> `message`	2017-12-22 18:49:36 -08:00