Regarding Shared Dll file inclusions

Hi, I got one application to be packaged that requires msflxgrd.ocx ver & there is a higher version of Merge Module available for the same DLL, So can we use the higher version available i.e include the latest merge module?
Wont it affect the application functionality?

Can you provide me steps to use if we have a lower version of DLL to be used and a higher present on the system?
Assuming the application is compatible with lower version of DLL and one application is compatible with higher version?

Thanks for clarifying,

0 Comments   [ + ] Show comments

Answers (2)

Posted by: anonymous_9363 12 years ago
Red Belt
Wont it affect the application functionality? How would anybody - bar the developer - know? You'd have to try it and see. To be fair, though, MS controls have a reasonable track record with backward compatibility so I'd give a tentative go-ahead, pending UAT.
Posted by: MSI* 12 years ago
Senior Yellow Belt
Hi there,

Why dont you try File Isolation..that would let you use a lower version without chnaging anything on share location..

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ