Does adding a Web Service to my ASP.NET MVC project break the whole concept of MVC?
That Web Service (WCF) depends on the Model layer from my MVC project to communicate with the back-end (so it looks to me like it needs to be part of the MVC solution).
Should I add this to the Controller or Model layer?
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
It sounds like you should split out your model into its own assembly and reference it from your MVC-application and WCF-application.
- YourApp.Data — Shared model and data access maybe
- YourApp.Web — If you want to share more across your web-apps
- YourApp.Web.Mvc
- YourApp.Web.WebService
If you want to do WebServices MVC-style maybe you should use MVC to build your own REST-application.
Method 2
Is there a specific reason you need to add web services to your MVC application? Unless there is a specific reason you should use your controllers in a RESTful manner just as you would a RESTful web service.
Check out this post from Rob Connery for more information:
ASP.Net MVC: Using RESTful architecture
Method 3
Separating the Model into it’s own project is not breaking the “MVC” pattern. First off, it is just that — a pattern. The intention of the MVC pattern is to clearly delineate between your data, the data handlers, and the presenters and the way you interface between them. The best way to do it is how Seb suggested:
- YourApp.Data
- YourApp.Web.Mvc
- YourApp.Web.WebService
Something that might help you out is the MVC Storefront that Rob Conery put together. Go watch the video’s here:
And if you want to look at the actual code in your browser to quickly see how he did it, go here:
MVC Storefront Codeplex Code Browser
Method 4
I don’t think separating the model into it’s own assembly has any bearing on whether or not you’re using MVC, you still have a model. Where it is is irrelevant surely?
Method 5
I’ve had a go at doing this.
See my result at my blog
ps: I don’t believe that this will break the MVC concept so long as you think that a web service is the model of a repository because all a web service does is returning a XML dump.
Method 6
I have added web services to my application and it works well. I don’t believe it violates MVC because it is an alternative interface to your model. MVC is not appropriate for web services because web services don’t have a view.
Method 7
Think of web services and databases as one in the same. Under this analogy, I think it makes sense to place your web service ingteractions where you place your database logic.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0