Geek Answers Handbook

Architecture / Structure of the ASP.NET Web Service

I am going to create a new asp.net web service (.NET framework 2.0), the functionality of the web service is to get the xml input, perform the corresponding operation (add / change / delete) based on the input and which indicate the status of the operation. I plan to implement a two-tier architecture (business level and database level) for this web service, can someone tell me if it will be the correct structure or any other structure will work well than that. Basically, I need some materials for designing a web service.

Thanks in advance.

Thanks Muru

+5
source share
3 answers

- , , - WCF ASP.NET.

:

, (Service), , -.

: WCF, ASMX, -.

+3

-, ASMX, .

DAL ADO LINQ ( , , - imo).

-? , ? JavaScript Ajax, , SOAP, xml.

- ASP.Net Ajax: -. , .

0

: / . Visual Studio, 4 5 :

1 webservice project.webservice( - , (-), -

1 project.service, (, , db ..)

1 , project.datalayer, ADO.Net Entity.

1 with dataclasses called project.model. These classes are those that are returned by the ADO.Net code and are used by the webservice service and project. If I use an entity structure, I usually skip this project because EF itself gives me the dataclasses that EF generates. Sometimes clients do not want to use Dataclasses EF, then I create a project.model project and let datalayer convert Dataclasses EF to project.model dataclasses

1 with a test project called project.test

hop it helps

Michelle

0
source

More articles:


All Articles