locked
Thoughts on best approach for parallel develop and then installation of web services

    Question

  • Within our company, we have hit a milestone to where we are finally able to reuse many of our web services.  The issue we are now facing is that with parallel development occuring on a single web service due to parallel projects, we are stepping on each others toes.  For example, assume you have a single web service application with two asmx pages:  Foo1 & Foo2.

    Both pages are being worked on for different projects each with a different timeline.  What we would like to do is to only have the deliverable to QA be only the code for the pages (asmx & Dll) that are related to the particular project.  What we currently due is to recompile the entire web service and deploy via MSI.  We no longer want to keep recompiling and re-deploying the entire web service; just the specific components that change.  Is there another approach that we should be considering/using given this new scenario.

    We are currently using Visual Studio 2008 & TFS for coding/versioning.  We have been using the VS2008 Setup Project to create the MSIs. 

    Thanks for any feedback you may provide.

    Thursday, April 05, 2012 9:35 PM

All replies

  • Hello,

    Check out the links below for starters. It may help you.

    http://aspalliance.com/1167_A_StepbyStep_Approach_to_Creating_a_Web_Service_Task_Using_SQL_Server_Integration_Services.3

    http://oracled.wordpress.com/2009/12/25/developing-web-service-top-down-vs-bottom-up-approach/

    Monday, April 16, 2012 8:42 AM