X
PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 25 Jan 2012 02:53 PM by  anon
Mesa DLLs Compliant with Applications Built Using Visual Studio 2010
 1 Replies
Sort:
You are not authorized to post a reply.
Author Messages

anon



New Member


Posts:
New Member


--
25 Jan 2012 02:53 PM
    It appears the Mesa DLLs were built using Visual Studio 2005 and contain no embedded manifest information for specifying the C runtime associated with Visual Studio 2005. Regretfully, C++ applications built using Visual Studio 2010 which want to use IDL, require that the MESA DLLs either 1) have embedded manifest information, or 2) be built using Visual Studio 2010. 1) Are there any plans to provide the Mesa DLLs with embedded manifest information, such that the Mesa DLLs can locate the runtime associated with Visual Studio 2005? 2) Are there any plans to provide the Mesa DLLs, built with Visual Studio 2010? Option 1 seems relatively easy, and the project i am on has tested/proved it works. However, when my plugin extension is installed at customer site, the customer will not allow us to overwrite their installed IDL Mesa DLLs with our patched version of the IDL Mesa DLLs. (FWIW: This is an extension to Opticks (http://opticks.org/conflu...Welcome+To+Opticks)) I have verified that IDL 7.1, and 8.0 have this problem. I do not have 8.1 available to me to see if this has been addressed in 8.1. Any help/discussion would be appreciated, Bob

    Deleted User



    New Member


    Posts:21
    New Member


    --
    26 Jan 2012 02:28 PM
    Hi Bob, You are absolutely right. IDL 8.1 and earlier were all built with VS 2005. In IDL 8.2 we rebuilt everything using VS 2010, so that should no longer be a problem. I agree that your "Option 1" is fairly straightforward, but as you point out, many customers do not want to modify their IDL installations. I would say your best bet is to wait until IDL 8.2 comes out (within the April/May timeframe), and then have your customers upgrade to that version. Thanks for reporting the issue. Cheers, Chris Exelis VIS
    You are not authorized to post a reply.