We have been scratching our heads over this now for about a week, so I thought I'd post something here and see if anyone has any insights. This *may* be a bug in 6.3v2, but I'm not 100% certain.
We have a custom format Read Operator that has worked just fine under 6.2 for many months. It's compiled in VS2005, with all the standard options. In attempting to get the Op working under 6.3, all we did was make a copy of the project directory, and change the VS project options to point to the proper 6.3 locations for the header and library files, and rebuilt. The build looked flawless. However, when we try to utilize the fle type, the node ERRORs, and the following is placed in the Application Error Log: Activation context generation failed for ...Reader.dll". Dependent Assembly Microsoft.VC80.DebugCRT,processorArchitecture="amd64",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762" could not be found. Please use sxstrace.exe for detailed diagnosis. Now, the reason the node is failing, as in clearly indicated in the error message, is due to the absence of the 'DebugCRT' dll for VS 2005 on the target machine (present of course, on the dev machine). Thing is, our plugin isn't compiled in debug mode, has none of the debug flags set, and the identical project has worked perfectly with 6.2. This leaves me to suspect that some library, or some subsystem of the 6.3v2 release has been compiled in debug, and this is causing the SxS to look for the dll. (The only libraries we include, by the way, are DDImage.lib and glew32.lib.) Thoughts, anyone? We really need to resolve this, since at the moment it is precluding us using 6.3 Steve
_______________________________________________ Nuke-dev mailing list Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
