I see. I don't know why we don't look for that registry entry, but it sounds like a good suggestion. Most users probably don't utilize these macros, instead using the Make VS.NET and VS.NET Get Version actions (which locate what they need differently), and I suspect that's why this issue wasn't noticed before. Thanks for the feedback.
|