On 12/09/2012 18:48, Alok wrote:
We had this in VS2010 for 2012 but I am not sure about 2013. Basically what we did was to use our own MACROS or variable instead of the one from setenv.bat. All you need to do is take your project generated from the wizard , start visual studio normally with call to setenv.bat and make your own solution and in the properties set the paths for include and libs for XSI manually. That should not work. At least it did for us.
Thanks Alok. Will try that...
