/build/static/layout/Breadcrumb_cap_w.png

Allow only one executable per component

I did a Setup Capture with Wise Studio. I have 2 Components that are red. Both show the error is that it contains more than one executable (EXE, DLL, OCX) and Microsoft guidelines allow for only 1 executable per Component. Is the solution to this really this simple:
1.) Right-Click one of the files and view it's Details to see what folder it should install into.
2.) Right-Click top Component tree and choose New > Component.
3.) Give the new component a name and choose the destination folder.
4.) Drag and drop the file into the new component.
5.) Go into the new Component and Right-Click the file and choose Set as Key
Thanks,
Troy

0 Comments   [ + ] Show comments

Answers (3)

Posted by: anonymous_9363 14 years ago
Red Belt
0
Wise doesn't do any validation checking per se after a capture. You have to set a validation process running.

The components are red not because there's more than one EXE but because the component has no key path set.

BTW, this forum is really for questions about errors returned by the WI engine (e.g. 1603, 1721 and so on). You ought to have posted in the 'Package Development' forum. A moderator may move it at some point.
Posted by: troy_in_wi 14 years ago
Orange Belt
0
VBScab,
You are correct, I should have posted it in Package Development. Sorry, my bad.
The 2 initial Components were red because they had more than one executable in them. By following my steps, it appears to have fixed them.
Now I wonder if there is a faster way to do it. One of my Components has 19 executables in it. That's a lot of 5-step repitition.
Posted by: zipsantro 14 years ago
Purple Belt
0
There is way in Wise where you can specify "Component Rule" to "One File per Component".
To Set open Windows Installer Editor --> Components Rule Menu -> Select Rule Set and Select Rule Set Name as "One file per component".
Make sure that you do this change before taking your capture. Now onwards you get only one file per component.

This a Recomended way and a best practice to follow.

Jeeoo!
Santro
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

Share

 
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