rittjc wrote: I mean the release of VS2010 was almost 3 years after the release of VS2008. I believe they did get in some fairly hefty service packs in between. I'd argue that's the right approach, as otherwise many customers (non-MSDN-subscribers) would need to buy a new copy each bl**dy time. Saying that, I'm no big fan of MSBuild generally - seems to me that the evolvution of build tools has been too influenced by the verbosity of XML. Too many of the rules for tools etc. are hidden in include files (to give them a more honest name) and the documentation is not great (often referring to some MS Press book)

I was thinking of writing an add-in which would allow this but I don't have a copy of VS so I can't :sigh:.  Maybe in a few months if I buy a copy :rolleyes: As of how to accomplish this I wouldn't have a clue at the moment and I'm too lazy to google it

Thanks Eric. That is a very inelegant solution. Looks like I am stuck with using it. Surprizing that there is not a better way. What if the end user does not have ADO 2.7 on his machine? Great job finding that buddy! It confirms the problem and at least offers a solution, elegant or not. Thanks again.