Umbraco Surface Controllers: Are you as confused as me?
I've seen lots of conflicting documentation about Surface Controllers. Some stating that you no longer have to append your controller class name with "SurfaceController", others that you do. Some stating that the controller is auto-routed to "/controller/action/id", others that it's "/umbraco/surface/controller/action/id"... I can't get either to work, honestly...
Also, what is the relationship of partial view macros to surface controllers or templates? I mean, what exactly is their function anyway?
Right now it seems there are half a dozen ways to create forms and MVC-like solutions with Umbraco but which approach is the right one in particular situations? I'm dizzy just trying to figure that out. It used to be so simple... If you wanted a form, you used a user control. Done.
Someone really needs to clarify all these questions and issues. I can't be the only one who is uncertain which approach to use or which documentation is authorative.
Umbraco Surface Controllers: Are you as confused as me?
I've seen lots of conflicting documentation about Surface Controllers. Some stating that you no longer have to append your controller class name with "SurfaceController", others that you do. Some stating that the controller is auto-routed to "/controller/action/id", others that it's "/umbraco/surface/controller/action/id"... I can't get either to work, honestly...
Also, what is the relationship of partial view macros to surface controllers or templates? I mean, what exactly is their function anyway?
Right now it seems there are half a dozen ways to create forms and MVC-like solutions with Umbraco but which approach is the right one in particular situations? I'm dizzy just trying to figure that out. It used to be so simple... If you wanted a form, you used a user control. Done.
Someone really needs to clarify all these questions and issues. I can't be the only one who is uncertain which approach to use or which documentation is authorative.
is working on a reply...