ASP.Net WebAPI controller in separate Class Library

Question

I am developing a new large Web Application using ASP.NET Web API. In that, I want to separate all controller classes into one different class library from ASP.NET MVC project.. Please consider following options.

Case 1 : Keeping controllers in same ASP.NET MVC project

Case 2 : Separating controllers in separate class library

Is it right to go with Case#1 as I think this controller can be reusable by other projects or hosting in windows service instead of IIS Web Application.
Also if in future if I want to access Web-API methods from Android,IPhone native apps then does it works for me in both cases Case#1 and Case#2
Is there any performance issue with Case#2.
What would be the best practice to register multiple controllers in both cases using UnityContainer.RegisterType ?

Careful of creating dependencies across DLLs, i.e. is that ok for you? — Paul Zahra, Feb 27 '14 at 11:39
Many tiny assemblies delay load time, and unity isn't the fastest container out there... — Hylaean, Feb 27 '14 at 11:45
Have a look here: http://odetocode.com/blogs/scott/archive/2013/07/01/on-the-coexistence-of-asp-net-mvc-and-webapi.aspx — Casper Skoubo, Feb 27 '14 at 12:20

score 4 · Answer 1 · answered Feb 27 '14 at 12:34

4

Putting your Web API code in a different project than your MVC code should be a best practice. There is no reason not to do it.

answered Feb 27 '14 at 12:34

Darrel Miller

139,164
32
194
243

ASP.Net WebAPI controller in separate Class Library

1 Answers1