I have a dll which is used by several application. The Problem => When there is a new build for the Dll ...all the other dependent application has a new build. So , all the apps has to go through the QA testiong steps. Result => A lot of wastage of time and resources. What should be the approach here ???? -- -R
Either you need to have a way to automate your regression testing or release the dll in iterative versions so that you can gracefully upgrade the dependent applications as needed or as time permits. -- Bryan Phillips MCT, MCSD, MCDBA, MCSE Microsoft MVP - Client Application Development Blog: http://bphillips76.spaces.live.com Web Site: http://www.composablesystems.net "-R" wrote in message news:F03F4A3A-9C9C-46A1-BD3F-8C9BA20AF15A@microsoft.com: > I have a dll which is used by several application. > > The Problem => When there is a new build for the Dll ...all the other > dependent application has a new build. So , all the apps has to go through > the QA testiong steps. > > Result => A lot of wastage of time and resources. > > What should be the approach here ???? > -- > -R