dgunthor
asked on
ole type library problem
hi,
i have enabled ole automation support in my mfc dialog application (vc6.0). when i build the debug version it creates a .tlb type library file but when i build the release version it doesn't. so whenever i launch my application using ole it launches the debug version.
how can i build the release version properly?
thanks,
dave
i have enabled ole automation support in my mfc dialog application (vc6.0). when i build the debug version it creates a .tlb type library file but when i build the release version it doesn't. so whenever i launch my application using ole it launches the debug version.
how can i build the release version properly?
thanks,
dave
Did you enable ole automatation in both the release and debug versions? I don't have 6.0 yet (should arrive tomorrow), but in 5.0 when you set the configuration, there is a drop down list called "settings for" at the top of the dialog that indicates what configuration (release or debug) that you are altering.
stupid question but
Did you register the release version
what happens when you execute your release version with the
commandline parameter /Embedding ?
Did you register the release version
what happens when you execute your release version with the
commandline parameter /Embedding ?
ASKER
hi nietod,
ole is enabled in both versions. i am using vb to launch the app using an ole call. this launches the debug exe of my application *always*. i guess it is something to do with the ole type library.
hi norbert,
i'm not sure what you mean by 'did i register the release version'. i only have one registry file (.reg) and it is not debug or release specific.
if i launch the application with /Embedding on the command line it runs fine. i'm not sure what this does though.
regards,
dave
ole is enabled in both versions. i am using vb to launch the app using an ole call. this launches the debug exe of my application *always*. i guess it is something to do with the ole type library.
hi norbert,
i'm not sure what you mean by 'did i register the release version'. i only have one registry file (.reg) and it is not debug or release specific.
if i launch the application with /Embedding on the command line it runs fine. i'm not sure what this does though.
regards,
dave
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
yep, spot on. when i run the application in release mode then call it using vb it works fine.
thanks,
dave
thanks,
dave