This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Registering SystemFolder Files
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 28, 2009
01:35 PM
Registering SystemFolder Files
Hello, I am very new to IS Pro, and I have a Basic MSI Project.
I have about 10 dll/ocx files that get placed in the SystemFolder location, however they do not get registered.
After I manually registered the libraries, my program launched. Where exactly do I set these to be registered? Thanks,
I have about 10 dll/ocx files that get placed in the SystemFolder location, however they do not get registered.
After I manually registered the libraries, my program launched. Where exactly do I set these to be registered? Thanks,
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 29, 2009
09:24 AM
First, and not exactly what you were asking, I think you might want to reconsider installing to the SystemFolder, as that isn't really recommended.
Assuming you want to do that, though, you can use COM extraction to insert the registration entries into your MSI tables, which is the recommended way to register COM files.
If you don't want to do that for some reason, you can also look into setting those files to use self-registration.
I'd suggest looking in the InstallShield help on those topics for detailed information.
Good luck!
Assuming you want to do that, though, you can use COM extraction to insert the registration entries into your MSI tables, which is the recommended way to register COM files.
If you don't want to do that for some reason, you can also look into setting those files to use self-registration.
I'd suggest looking in the InstallShield help on those topics for detailed information.
Good luck!
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 29, 2009
02:31 PM
Ok thanks for the recommendations
What exactly is the problem with using the System Folder? I'm converting a basic Visual Studio installer project to IS2010, and that is how the developer was doing it. He doesn't like to change things without reason. Are there known issues with using the SystemFolder?
One of the COMs being placed there is a dll we have created, but the others appear to be normal windows things like SYSINFO.ocx and SetACL.ocx
What exactly is the problem with using the System Folder? I'm converting a basic Visual Studio installer project to IS2010, and that is how the developer was doing it. He doesn't like to change things without reason. Are there known issues with using the SystemFolder?
One of the COMs being placed there is a dll we have created, but the others appear to be normal windows things like SYSINFO.ocx and SetACL.ocx
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Sep 29, 2009
02:41 PM
The SystemFolder by best practice rules is for permanent files used by system level applications. Meaning that these files generally will not be removed or updated. For more commonly updated shared files they recommend you use the common files folder or create some custom defined default location your applications can be directed to search in.