Most of the ASP.NET MVC examples I have seen depict scenarios where a user is viewing an object (or collection of objects) and then moves from that page to one that displays a form that the user completes. Upon submitting the form with good input, the user is redirected back to the page that shows the object (or list) and the user can see that their changes were successful.
I've run into a scenario where there is no view or list page per business rules.
What are some good approaches for this scenario in ASP.NET MVC?
In the old days with Classic ASP and ASP.NET, I would process the input and then show the user a success message or the form with errors - all from the same page. This seems like it goes against best practices (SRP, no logic in views, etc.).
One easy approach is to redirect to a new page that tells the user their changes were successful, but then the user can visit that page any time. If I start putting in logic to protect against this (i.e. tempdata), the solution starts to feel dirty.
I could redirect to a landing page but there is no confirmation. Maybe I could rely on a messaging system that shows the end user a confirmation when they return to the landing page?