I have a bit of a conceptual problem with AI... It is not as intuitive as I'd hopped it would be. And help is not written very well. Because of that I need some clariffications... many of them
So,,, I have a package that I need to deploy several dll files and ocx files with. That is all fine,,, I package them no problem... however,, those files need to be registered with the OS.
Here is a whole range of issues.....
If I set the components to auto register,,, then on VIsta and XP,,, the components registrations fail, which prevents the instillation to go through. This is a good thing and it is supposed to happen because Vista and XP will automatically prevent the components that exist and are registered to be overwritten. So the issue is NOT in my dll's or OS... the issue is in the installer that is attempting to register components which exist and are already registered.
Then,, If I set the components to NOT auto-register,,, WHAT DOES THAT MEAN? Will the register if they don't exist or will they simply NOT REGISTER?
I can't find a single reference in help files that explains this.
Then,,, If I set the components to "Never Overwrite",,, things seem to start making sense,, but then I am not sure how to combine all this?
Should I set the components to auto-register OR Not?
Will they register automatically if they don't exist?
If I set them to auto-register and to "never overwrite" does that mean that Vista installation will work fine?
ALSO
When I set the installer to "Run only if user has administrator privileges" what exactly does this mean.... Is the msi package set to work as INVOKER or forces admin?
I mean,,, your software seems to do a lot of cool stuff but your help sucks. I have wasted 3 days on this.
I would really appreciate a concise and clear explanation on these issues.
FOLLOW US
Get the latest news in Application Packaging