This does not include the deployment helper on mono. So the test needs to point to a statically deployed application url to run.
There are some bugs in mono Httpclient like in case of 302's RequestMessage's Uri not modified, cookies not cleared in cookie container etc. I will file bugs in mono on those and this is a work around until then.
There is still more work and refactoring. This is a first step.
- can't be done as a unit test because `k.cmd test` doesn't write assemblies for referenced projects
- instead support extending the "test" target in builds
To enable this in a repo, add the following to the makefile.shade file:
```
#xml-docs-test target='test'
k-xml-docs-test
```
Example output with one syntax error and one invalid reference:
```
info: Target xml-docs-test
warn: Invalid documentation syntax in src\Microsoft.AspNet.Mvc.Core\bin\debug\net45\Microsoft.AspNet.Mvc.Core.xml
warn: 3170: <!-- Badly formed XML comment ignored for member "T:Microsoft.AspNet.Mvc.Rendering.HtmlHelper" -->
warn: 3203: If the object is already an <see cref="!:IDictionaries<string, object>"/> instance, then it is
```
- no need to call (`internal`) `html.GenerateId()` method since it matches `html.Id()` exactly
- no need for `.ToString()` with either method since they return `string` now
The original sample used @Html.DisplayFor. While porting I changed it to use ValueFor. Xinyang pointed out this difference.
Fixing this so that it can be easily compared with the original sample. The results of the view unchanged.
Removing the Layout page reference from individual cshtml files.
Added some tests to verify layout getting rendered in every view.
Added a couple of verifications to verify that title of the page is set appropriately.
Levi B
Praburaj
Pranav K
ajcvickers
David Fowler
dougbu
Pinpoint
Suhas Joshi