who did the compiling? because there’s an ordeal of options and includes you can setup and change, and you could need to setup the pragmas and linking differently.
the lack or presence of a runtime library doesn’t mean anything from an IDE point of view since it can be fetched from the previous version or from an online library and eventually included in the packaging.
I take that for the custom shader part you are mostly referring to Stefano’s work, did you try and ask him if he can rectify the problem?
which library is that? because frankly all the work we did recently on a couple of movies involved A LOT of custom shaders, some by Andy and of a certain level, and we always used VS.net.
I suspect you are confusing what really is a project related problem (working on a project that started on a different IDE) with an IDE related problem(that is not).
fishing up somebody else’s stuff and failing to compile it is a sign of poor retrocompatibility of VS.net with VS6 maybe, but the benchmark for compatibility between VS.net and XSI/MRay is starting with a new project.
last but not least VC++6’s compiler is laughable, especially in its lack of comformity to standards, with projects made to work in VC++6 I often had projects that needed a lot of tweaking to compile under linux with GCC, insofar everything I’ve done or seen done in VS.net has always compiled straigth away in Linux.
glad to see you are starting to pick up proper C++ development as well.