...Thank you for you reply.Well now I am trapped. If until now I was deleting the tt.log as a workaround now I simply have no way out. Your alternate solution is not viable since in our scenario one code generation round generates several files, each in
a different project...
Another workaround that may help is to centralize all generated output in a shared custom class library project.
After doing that, one can have all the generated output files in one place and simply add a file-based-reference or a project-based-reference in the consuming projects.
Of course, that may not SEEM to work for you.
However, with this suggestion, and with the suggestion above, consider that the suggestion is just a launching-pad for you consider alernate ways of attacking the problem, which often leads to a solution.
That is, "be bold" and "be courageous" with your coding. If it is THAT hard to rearchitect, even for a test, then that may be design-smell, as is the case at my end.
-- Mark Kamoski