DrJones
Posts: 18
Joined: Wed Jun 28, 2006 10:00 pm

Various questions

We've always had a few quirks to work with in getting Advanced Installer to work as we want it too. There are fewer quirks than the other options, which is why we use it, but I was curious if any of the following things are fixed in the latest version (we are deciding if we should renew our license and upgrade from 6.8).

We have a simple hardware device (USB using WinUSB) and if we install the driver with the installer (as we need to) then each time the user upgrades to a new version, they have to reconnect their devices and go back through the add new hardware wizard each time. I know we can create a separate installer package to deal with this and use it as a prerequisite (which we've done before) but that causes extra steps during the process and isn't ideal.

Next, every time we build a new installer we have to update version numbers for all our .dlls and .exes. If we didn't do this, when we upgraded and ran a newer installer the old items would be removed, but the new ones wouldn't be installed (the .dll and .exes are .NET). It's a little silly to have to rebuild all our applications for each release, even when we don't actually make any changes to them.

When we update version numbers of our .NET .dll, we have to manually remove and read the entries from the assemblies page, it doesn't automatically adjust to the changed version number. We also have to do it for both, since we need to have two copies of the same file, one to place into a folder (so Visual Studio can find it) and one installed into the GAC.

Are any of these issues now fixed or being worked on?
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Various questions

Hi,
We have a simple hardware device (USB using WinUSB) and if we install the driver with the installer (as we need to) then each time the user upgrades to a new version, they have to reconnect their devices and go back through the add new hardware wizard each time. I know we can create a separate installer package to deal with this and use it as a prerequisite (which we've done before) but that causes extra steps during the process and isn't ideal.
You can try using the "Install new version first and then uninstall old version" option in the Upgrades page. This should avoid the reinstalling of the service. Note that in order for this to work the component names and GUIDs should not change from one version to another.
Next, every time we build a new installer we have to update version numbers for all our .dlls and .exes. If we didn't do this, when we upgraded and ran a newer installer the old items would be removed, but the new ones wouldn't be installed (the .dll and .exes are .NET). It's a little silly to have to rebuild all our applications for each release, even when we don't actually make any changes to them.
The option I mentioned should also take care of this Windows Installer bug. Another approach is to use the "Ensure that all files in this folder overwrite any installed target files" option in the Properties tab of the "Edit Folder" dialog.
When we update version numbers of our .NET .dll, we have to manually remove and read the entries from the assemblies page, it doesn't automatically adjust to the changed version number. We also have to do it for both, since we need to have two copies of the same file, one to place into a folder (so Visual Studio can find it) and one installed into the GAC.
This improvement is on our TODO list and it will be available in a future version.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”