This repository has been archived by the owner on Dec 14, 2018. It is now read-only.
Html.AntiForgeryToken helper throws exception on Mono #847
Comments
@harshgMSFT please go ahead and make the change (preferably this week) |
Prabu can you please verify and close? |
This can be closed. If this is the same as the private that I tested, I can confirm this worked. |
dougbu
added a commit
that referenced
this issue
Aug 1, 2014
…)` return `string` - fixes #566 and part of #847 - allows compositions such as `@Html.Label("property", Html.Id("property"))` and `@Html.Raw(Html.DisplayText("property"))` (this one is not recommended) - adjust XML comments to match - add missing XML comments to `HtmlHelperValueExtensions` - nit: `TInnerModel` -> `TModelItem` - increase XML comment consistency for changed methods - generally make wording more consistent e.g. how we use words such as "returns" - use `<see langref="string|true|false|null"/>` more
dougbu
added a commit
that referenced
this issue
Aug 2, 2014
…)` return `string` - fixes #566 and part of #847 - allows compositions such as `@Html.Label("property", Html.Id("property"))` and `@Html.Raw(Html.DisplayText("property"))` (this one is not recommended) - adjust XML comments to match - add missing XML comments to `HtmlHelperValueExtensions` - nit: `TInnerModel` -> `TModelItem` - increase XML comment consistency for changed methods - generally make wording more consistent e.g. how we use words such as "returns" - use `<see langref="string|true|false|null"/>` more
dougbu
added a commit
that referenced
this issue
Aug 5, 2014
- don't call other extension methods - #847 line 7 - remove extension methods that do nothing but pass through to the interface method - weren't exactly ambiguous (interface method wins) but were useless
dougbu
added a commit
that referenced
this issue
Aug 6, 2014
- don't call other extension methods - #847 line 7 - remove extension methods that do nothing but pass through to the interface method - weren't exactly ambiguous (interface method wins) but were useless
dougbu
added a commit
that referenced
this issue
Aug 9, 2014
- #847 line 1: copy XML comments from interfaces to extension methods - lots of wording changes to be more consistent - core text split from PR #866, where @rynowak and I hashed out the words - to extent possible, reuse words between method descriptions - add `<remarks>` describing behaviour of input helpers e.g. `CheckBox()` - add a few missing `<param/>` and `<typeparam/>` elements and fill in empty ones - display more HTML elements as tags - use `<c>true|false|null</c>` more often nits: - "The expression" -> "An expression" - make examples for `ObjectToDictionary()` and `AnonymousObjectToHtmlAttributes()` more consistent - move `<typeparam/>` elements (that existed) after all `<param/>` elements
dougbu
added a commit
that referenced
this issue
Aug 12, 2014
- #847 line 1: copy XML comments from interfaces to extension methods - lots of wording changes to be more consistent - core text split from PR #866, where @rynowak and I hashed out the words - to extent possible, reuse words between method descriptions - add `<remarks>` describing behaviour of input helpers e.g. `CheckBox()` - add a few missing `<param/>` and `<typeparam/>` elements and fill in empty ones - display more HTML elements as tags - use `<c>true|false|null</c>` more often nits: - "The expression" -> "An expression" - make examples for `ObjectToDictionary()` and `AnonymousObjectToHtmlAttributes()` more consistent - move `<typeparam/>` elements (that existed) after all `<param/>` elements
dougbu
added a commit
that referenced
this issue
Aug 12, 2014
- #847 line 1: copy XML comments from interfaces to extension methods - lots of wording changes to be more consistent - core text split from PR #866, where @rynowak and I hashed out the words - to extent possible, reuse words between method descriptions - add `<remarks>` describing behaviour of input helpers e.g. `CheckBox()` - add a few missing `<param/>` and `<typeparam/>` elements and fill in empty ones - display more HTML elements as tags - use `<c>true|false|null</c>` more often nits: - "The expression" -> "An expression" - make examples for `ObjectToDictionary()` and `AnonymousObjectToHtmlAttributes()` more consistent - move `<typeparam/>` elements (that existed) after all `<param/>` elements
dougbu
added a commit
that referenced
this issue
Aug 14, 2014
- #847 line 1: copy XML comments from interfaces to extension methods - lots of wording changes to be more consistent - core text split from PR #866, where @rynowak and I hashed out the words - to extent possible, reuse words between method descriptions - add a few missing `<param/>` and `<typeparam/>` elements and fill in empty ones - display more HTML elements as tags - use `<c>true|false|null</c>` more often - add `<remarks/>` describing behaviour of input helpers e.g. `CheckBox()` - add `<remarks/>` explaining "renders" - add `<remarks/>` containing example expression names nits: - "The expression" -> "An expression" - make examples for `ObjectToDictionary()` and `AnonymousObjectToHtmlAttributes()` more consistent - move `<typeparam/>` elements (that existed) after all `<param/>` elements - explain "checked" attributes better, removing some duplicated words from the `RadioButton[For]()` descriptions - correct `routeValues` description in `GenerateForm()` comments
danroth27
changed the title
Html.AntiForgeryToken helper throws exception on mono
Html.AntiForgeryToken helper throws exception on Mono
Aug 17, 2014
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
https://github.com/aspnet/Mvc/blob/dev/src/Microsoft.AspNet.Mvc.Core/AntiForgery/BinaryBlob.cs#L96
Recommendation from Levi:
MVC should instead be using the RandomNumberGenerator class. CryptRand was just a temporary workaround because the CLR team didn’t have the crypto libraries ported over.
The text was updated successfully, but these errors were encountered: