Dev manager at Jungle Disk. I love fixing things, whether I’m refactoring or digging into bugs, I just find it satisfying to make things better than they were before.
Very, very cool post. I’ll definitely be checking out the “inspiration” article you referenced.
I would also definitely love to see this be the start of a series of posts covering the additional features you mentioned at the end. I’ve been curious about parsers for a while, just haven’t felt confident enough to dive in. This would be a great intro on the subject, as well as a great concrete “application” of a parser.
Curious if you would also be willing to go into some example scenarios where a custom view engine would be a useful choice.
I'm glad you liked it and thanks for reading! I do plan to write additional posts on some of the points mentioned at the end.
A custom view could be useful if the target output is not HTML (e.g. XML) as Razor is geared towards rendering HTML. Furthermore, it may not be desirable to mix server-side and client-side code. If a project is being ported from a different language or framework that uses a different template system, it may be easier to retain the existing views.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Very, very cool post. I’ll definitely be checking out the “inspiration” article you referenced.
I would also definitely love to see this be the start of a series of posts covering the additional features you mentioned at the end. I’ve been curious about parsers for a while, just haven’t felt confident enough to dive in. This would be a great intro on the subject, as well as a great concrete “application” of a parser.
Curious if you would also be willing to go into some example scenarios where a custom view engine would be a useful choice.
Thanks!!
I'm glad you liked it and thanks for reading! I do plan to write additional posts on some of the points mentioned at the end.
A custom view could be useful if the target output is not HTML (e.g. XML) as Razor is geared towards rendering HTML. Furthermore, it may not be desirable to mix server-side and client-side code. If a project is being ported from a different language or framework that uses a different template system, it may be easier to retain the existing views.