title: Handling business rule exceptions in business logic layer
body: <p>What's the best way to handle business logic violations/exceptions in my ASP.NET MVC app? Do I throw an exception with an Http status code?</p>
  
  <p>In my application, I have multiple projects e.g. MVC, business logic, DAL/Infrastructure, etc.</p>
  
  <p>Let's say, I get a request from a user who is not authorized to see that information. I figure out that the user is not authorized in the business logic layer which is a class library project. What's the right way to tell the MVC front end that the user is not authorized to get that information?</p>