Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

4

I realize this is dead and over, but couldn't help remarking that your own answer here is the perfect argument for why YOU [hopefully went] with Razor and not XSL: you're clearly more comfortable with the imperative programming paradigm that Razor sticks to versus the declarative (quasi-functional) model that XSLT is at its best (& hardest) in. e.g. instead of template matching name (possibly dropping to a different mode), you ran a for-each across it from item. While this technically works, it fails to play to XSLT's strengths. This should not be downplayed as a (personal) argument.

taswyn
– taswyn

2015-07-17 20:41:50 +00:00
Commented Jul 17, 2015 at 20:41

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »