471,337 Members | 1,342 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,337 software developers and data experts.

Shared Component Installation

Our application also includes a Merge Module of our own. Some of the
utilities that sit in <commonfiles> area are also intended for consumption by
external third parties. Hence these were candidates for MSM. When I created
this MSM, I also specified intended target folder as <commonfiles>\vendorname
and additionally specified MS redistributable MSMs such as ATL7.1, MFC7.1 etc
as additional dependencies on my MSM! The trouble is, when I create a merge
module of our own, I can only state its dependencies - I can't specify target
folder for these dependencies. I can only specify target folder for my
components, not for the dependent MSMs! This adds a further interesting
twist. I find MS files end up in <installdir> folder (program
files\vendor\app) although my own MSM components go to my suggested
<commonfiles> target folder!
Jul 25 '05 #1
0 903

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

2 posts views Thread by Mervin Williams | last post: by
1 post views Thread by May | last post: by
1 post views Thread by webguynow | last post: by
reply views Thread by webguynow | last post: by
reply views Thread by rosydwin | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.