DotNetOpenAuth.WebAPI
DotNetOpenAuth.WebAPI copied to clipboard
DotNetOpenAuth for ASP.NET WebAPI (OpenID/OAuth/OAuth2)
Bumps [Newtonsoft.Json](https://github.com/JamesNK/Newtonsoft.Json) from 6.0.6 to 13.0.1. Release notes Sourced from Newtonsoft.Json's releases. 13.0.1 New feature - Add JsonSelectSettings with configuration for a regex timeout Change - Remove portable assemblies from...
Bumps [Newtonsoft.Json](https://github.com/JamesNK/Newtonsoft.Json) from 6.0.6 to 13.0.1. Release notes Sourced from Newtonsoft.Json's releases. 13.0.1 New feature - Add JsonSelectSettings with configuration for a regex timeout Change - Remove portable assemblies from...
Bumps [Newtonsoft.Json](https://github.com/JamesNK/Newtonsoft.Json) from 6.0.6 to 13.0.1. Release notes Sourced from Newtonsoft.Json's releases. 13.0.1 New feature - Add JsonSelectSettings with configuration for a regex timeout Change - Remove portable assemblies from...
Bumps bootstrap from 3.2.0 to 3.4.1. [](https://help.github.com/articles/configuring-automated-security-fixes) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...
Bumps bootstrap from 3.2.0 to 3.4.1. [](https://help.github.com/articles/configuring-automated-security-fixes) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a...
Hello, Visual Studio 2013's users have a problem with the restoration of nuget's package. This issue is known as the issue #5 . I follow some steps describe in [differents...
I tried to open the project in Visual Studio 2013 and it did not go well. I see errors like: packages\Microsoft.Bcl.Build.1.0.7\tools\Microsoft.Bcl.Build.targets was not found I believe that the issues relate...
Using HttpContext.Current is gennerally considered a bad thing for several reasons like mocking and testability. The following has proven to be working as an alternative: https://gist.github.com/3194281