We have a custom wizard used in VS2015 Profession and up. On one particular system with VS2015 Enterprise, the wizard fails on finding symbol setDirection, but on another system it works fine; all system with VS2015 Pro work fine too. The failing (and working) system use English versions of Windows 7 and VS.
Anyone have an idea what can cause this?
Thanks , Jan
Jan