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.
Microsoft réalise une enquête en ligne pour comprendre votre opinion sur le site Web de Msdn. Si vous choisissez de participer, l’enquête en ligne vous sera présentée lorsque vous quitterez le site Web de Msdn.