view resolution

[Mario Gutierrez]

So the resolution logic is currently this

 

• If the Web Service specifies a template (via a customized IHttpResult.TemplateName response) - then a View with that name.
• A view with the same name as the Response DTO, looking first in /Views then in /Views/Shared
• A view with the same name as the Request DTO, looking first in /Views then in /Views/Shared

I wonder if it would make more sense to search for Request DTO before Response DTO. As it is, if I have a Response DTO shared by many methods, I can no longer use a Request DTO as the name of a view template. It simply never gets used. Wouldn't it make more sense to search for Request DTO first, then Response DTO?

[Demis Bellot]

Yeah this was a tough call, because on the one hand the response must match the RazorView model - which is what Response DTO's do :)

And on the other the Request DTO's are unique, so I was thinking more along the lines of conventionally picking the most likeliest times the models will match - which is why I went with the Response DTO.

But I might change it seeing that Request DTO's are unique and can allow for your scenario of services re-using the same Response DTO with different views.

--
- Demis

http://twitter.com/demisbellot

http://www.servicestack.net/mythz_blog

[Demis Bellot]

ok i've swapped the order around in this commit: 

https://github.com/ServiceStack/ServiceStack/commit/86d74952817efffb3f5ba0405b1e1f5c693f0552

Should be available in the new release at the end of this week.