MVC or Extract Service Layer
we have an application that is built with .Net MVC. We are now tasked with exposing API’s to third parties. Members on our team want to just continue down our current path and just use more controllers so we can reuse the backend of our current application. Logic tells me we need to create a seperate service layer when more clients are going to be accessing it, but .Net MVC seems to take care of all of this. Is it really acceptable architecture to use controllers in a stand alone application to expose API’s and what would be the potential gains of extracting the service layer out?
WCF an Entity Framework connection
I have a 100+ users on a Silverlight application that uses WCF and entity framework.
Is passing the Model around in this way considered bad practice?
If I have a view called, for example, ViewDetails
that displays user information in labels and has a Model called ViewDetailsModel
and if I want to allow the user to click a button to edit some of these details, is it considered bad practice is I pass the entire Model in the markup to a controller method which then assigns the values for another model, using the values stored in the Model that was passed in as a parameter to that action method? If so, should there instead be a service method that gets the data required for the edit view?
Apply WCF For Large Projects [closed]
It’s difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center. Closed 11 years ago. We have a large project that has nearly […]
SOA in .NET 4.5 with MSMQ Durability
I have been doing some investigation regarding ASP.NET Web API. I have enjoyed using the WCF REST template to create new RESTful web services, and Web API seems to be a cleaner iteration on that.
Azure website that talks to third party services
I have website that crawls data from many third party services when user browse to webpage. This can be really slow because I hit third party server and process returned data before showing it to user. I am hosting website on Azure (shared mode). I am thinking to improve my implementation. Here is what I am thinking…
Implement service layer in MVC
We have a defined service layer hosted in WCF. We are now building a website that will need to use the services functionality. The website is being written in ASP.NET MVC 4 and I’m trying to decide how to reference the WCF service from the MVC app. It’s a large complex website and it will be changing on a weekly basis.
Interaction of a GUI-based App and Windows Service
I am working on personal project that will be designed to help manage my media library, specifically recordings created by Windows Media Center.
WCF service as a proxy for publishing real-time data to a WPF/MVVM clients
I’ve been tasked with creating a dashboard application to show real time updates for our servers. The raw data comes in from an XML file on our intranet which I need to parse and present to the user.
WCF hardware requirement
I read the hardware requirements of WCF in a book and two of them are the following ones: