ASP.NET MVC: Avoid Polluting The Model Of The View With Error Messages

I recently answered a question that came up on the StackOverflow website. The question was whether using the ViewBag dynamic property of the controller to expose the error message was a good practice, as the OP investigations suggested that it was necessary to expose properties from the model. Obviously it is highly recommended NOT to use the ViewBag property since it does not provide any Strong Typing. If you want to communicate with the view you should always involve a typed model. The suggested solution is therefore legitimate in that respect, however, it is not a good practice when it comes to model error handling in ASP.NET MVC. The solution for exposing error messages (as in the previous example, which does not use data annotation attributes) derives from the use of the AddModelError method, from the ModelStateDictionary class. We do not need to instantiate this class because a ModelState property containing an instance of this class already exists in the Controller. Therefore, the right solution is the following:...

Read more
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

Monthly Archives

Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))