467,169 Members | 1,075 Online
Bytes | Developer Community
Ask Question

Home New Posts Topics Members FAQ

Post your question to a community of 467,169 developers. It's quick & easy.

How to scope the number installed modules during installation time for each specific

Dear everybody,

I'm very sad now. I have problem with making the Setup package. Could you share with me a light.Our problem as followings:

1. I expect the deployment package contains the following features:

- The user will get the deployment package with 2 files: setupname.msi and setupname.ini

- The setupname.ini file tell us which modules the end user has permission to install (and which are not-allowed-modules).

- The setupname.ini is changed by our company and send it to customer along with the setupname.msi

2. My solution now is not good, we do as following:

- We implement a function in the CustomAction (concretely the Installer class in C#) in Install group. This function will read the setupname.ini in source folder and do deleting the "not-allowed-modules" at the end of install process.

3. Why I said my solution is not good:

- When user do repairing, the source folder path is empty. We cannot find the reason why so far. To get the source dir we now pass the source folder path through the customaction parameters (\path = "[SourceDir]/")

- When user install , the deployment package is unpacked and stored in the target folder on the end user's machine before the customaction can run. I'm afraid someone can hack it and play with our product

4. Question:

- How to get SourceDir when repairing ? Could you give me a sample source code please?
- I'm afraid very much about my bad solution, so could you please give us some advices. How to avoid that the Not-allowed-modules are unpacked and stored in the target folder?

Any help is highly appreciated.
Thank you and best regards
Vu Nguyen
Dec 11 '09 #1
  • viewed: 981

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

5 posts views Thread by elzacho | last post: by
6 posts views Thread by Washington | last post: by
6 posts views Thread by Ben Finney | last post: by
14 posts views Thread by Phil | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.