Thursday, March 24 2005 - blog
I'm curious about how people are building solutions using ASP.NET pages and ASMX web services today. Do you intermix .ASPX pages and .ASMX services together in the same site, or do you separate out the two different types of content into different virtual directories?
What pushes you toward one approach or the other?
I believe that you can accomplish a service layer without having physical separation. I intersperse the services within the aspx project. Granted, the services that my applications expose are typically not too much.I also look at some other factors that really shouldnt weigh in on this such as ease of deployment and maintainability.
I've done both, but in all honesty, I don't feel all that strongly about either one. One thing I do try to do is keep just a little bit of separation, like having services in designated folders (say, a /services/ subfolder of the site).
I've done both, but in all honesty, I don't feel all that strongly about either one. One thing I do try to do is keep just a little bit of separation, like having services in designated folders (say, a /services/ subfolder of the site).
I tend to separate the two, since I use .asmx as a service interface, and .aspx as UI.But that is mostly a personal preference in order to keep things logically tidy in the solution.Unless the service interface is going to be hosted on a completely separate physical tier, there doesn't seem to be an overwhelming argument to do it one way or the other.
We keep our web services in a separate project.I wouldn't get religious about where to put them, but I would at least put them in a separate folder like Tomas said.The WS layer is generally an abstraction layer.You may want to expose different abstractions that access the same underlying data.I would want to keep the abstractions grouped together in some way.
Definitely seperate. Logically they are two completely seperate layers: Presentation and Service. Also, you a future requirement may arise in which you must deploy your service on different hardware or a different application pool than your web application. This could be for reasons of security, performance, process isolation, or administration.
I'm delving into my first serious web services adventure and we're keeping it separate because in essence it's a separate project.The web service will provide the interface to the database and provide methods for maniplating the data (fancy versions of add/edit/delete).We're also building an ASP.NET application which will consume the web service to provide the interface for users.We know that in the future there will also be other interfaces (automated) which will also consume the web service.
By "separate", do you guys generally mean in separate folders underneath the same Virtual Directory (and hence the same AppDomain), or in completely different AppDomains?Sounds like a combination of both from what I'm hearing. Thanks for the responses so far!
When I talk about keeping them separate, I mean in separate AppDomains.In some cases, like my current project, the asmx's are hosted on a different physical tier...the same boxes that host the .NET remoting interfaces (different AppDomain) and the business and data abstraction components.
Usually, I put ASMX in a distinct subdirectory, to do that let me share Http Modules and some special treatment in Global.asax
Steve Maine • Design by Free CSS Templates. Ported to Graffiti by Brendon Schwartz. • Icons by FAMFAMFAM.
