Hi you could use a post build event in every VS project you have something like : echo $(ProjectName) > c:\watchfolder\$(ProjectName).txt
When the project is compiled, this (batch) file is also run now the watchfolder contains all project names that have been compiled I did not test it, just an idea that could work with kind regards Ruben Willems 2009/3/16 सिद्धार्थ <[email protected]> > > Hi, > > Can you please elaborate more on this. > I am not getting you. > > regards, > sid > > On Mar 16, 2:43 pm, Ruben Willems <[email protected]> wrote: > > Hi > > > > you could use a post build event to write some information to a file or > so, > > and check on that later on. But I always do a clear and acompile, so all > > projects get compiled and tested. > > > > just to be sure ;-) > > > > with kind regards > > Ruben Willems > > > > 2009/3/16 सिद्धार्थ <[email protected]> > > > > > > > > > > > > > Hi All, > > > > > Since MSBuild understands the dependencies between projects > > > > > - E.g. project A is only used by Project B. If there is a > > > change in A, only B needs to be tested, not all other applications > > > (e.g. C ). Can we use MSBuild to determine which projects need to be > > > tested after a commit ? > > > > > regards, > > > sid- Hide quoted text - > > > > - Show quoted text -
