.NET Framework Bookmark and Share   
 index > ASMX Web Services and XML Serialization > Patterns and practices for integration with web services
 

Patterns and practices for integration with web services

I have several web services that I need to communicate with. I am looking for patterns and practices for referencing these services.

At the moment I have wrapped each different web service with a dll. Then my business layer calls this dll when it needs information from the web service. So all the mapping between my business objects and the service objects is done in this 'service proxy'.

I'm not sure if this is the best approach. Do you have any suggestions?
TheLearner
"If it ain't broke, don't fix it"?

Are you seeing problems with your current approach? Do you foresee any?

I often create a Class Library project to which I add all my web references. The business layer can then access the class library.


John Saunders
WCF is Web Services. They are not two separate things.
Use WCF for All New Web Service Development, instead of legacy ASMX or obsolete WSE
Use File->New Project to create Web Service Projects
John Saunders
Yeah you're right. It seems to work fine just wanted to follow the best approach possible.
TheLearner

You can use google to search for other answers

Custom Search

More Threads

• How do I read mYsql data with ASP?
• Multiple Security Tokens
• Tabs on Webform
• xs:time XML type serialization bug
• Raising Events from the server to client using Web Services
• Associate custom serializer with class?
• Modify HTTP Header
• cannot connect to configuration database
• eConnect XML docs into GP
• Consuming Web services from SQL 2005 trigger