In the resulting file you will be able to see what happened with that file, and in particular whether windows installer decided not to update it. But first check whether the updated version is indeed in the installer. Got the logging worked out, there's a command line switch for the installshield LE setup exe that allows you to pass the logging parameters on to the msi. Looked at the log and didn't actually see my assembly getting installed.
Now I'm wondering if there's some assembly cache that it searched through when the installer didn't have the file At any rate, I modified my installer to explicitly include the offending project's primary output instead of relying on it to be picked up as a dependency and voila it worked. I'm marking yours as the answer because the logging was just what I needed! Community Bot 1 1 1 silver badge.
Christopher Painter Christopher Painter The strange thing is, the old version of the file can't be found anywhere on my machine.. I know you deleted all your bin and obj folders, but it's probably worth a try. If you find the problem reference, just remove and re-add it and you should be good. Brandon Dybala Brandon Dybala 2 2 silver badges 11 11 bronze badges.
All my references for the assemblies that have problems are 'project references'. As part of my sanity check, I did go through and verify each of the references.
Additionally, in the actual Bin folders, the correct version is present. It is only in the installer that the file gets reverted to an old version. WiX has e. UpgradeCode to help you control version checks on features.
Perhaps it can be of use. I've been thinking about making this transition for some time. The learning curve always steered me away in favor of something I could throw together more quickly. However, after years of frustration with the limitations of Setup Projects and now InstallShield LE, I can't imagine the total cost of a WiX implementation to be any higher.
Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. While this can be an initial cost saver in terms of sequencing effort you have to be aware of what you sacrifice with such a solution. Any special post configuration of the application will be missed because the conversion tool only has the MSI as a reference as to what the sequence will look like.
Other issues I would look for is the launching of the application after installation to properly define the virtual file system and virtual registry. If the MSI sets up an ActiveSetup routine to perform the user profile population your conversion will likely capture the ActiveSetup but not run it since it is the Windows logon process that executes ActiveSetup routines.
Or say your application has a launch script that needs to happen for a terminal server world to populate the user's home drive with data. Depending on how your MSI is set up it may miss this piece. I've been wanting to kick the tires on the InstallShield solution but these are things I would be checking for in a conversion tool to rate the output quality. There is a place for such solutions but forget the marketing speak for a moment and use your application packaging skill to predict some of the oddball stuff that occurs when packaging in a corporate environment.
Office Office Exchange Server. Not an IT pro? Resources for IT Professionals. Sign in. United States English. Ask a question. Quick access. Search related threads. In this section, you will learn how to install and configure the following types of files:. InstallShield provides methods for creating elements that can be used by multiple installation projects, and for combining multiple complete product installations.
Unlike traditional installations, Windows Installer installations do not use an explicit script, but instead perform actions arranged into your product's sequence tables. Like standard Windows Installer actions, your installation's user interface is controlled by MSI tables and actions. Windows Installer supports different types of updates and different techniques for packaging them for distribution. In this section, you will learn about additional functionality of InstallShield and Windows Installer, including:.
In this class you will learn how to: Create and organize an installation project Install files and create shortcuts Install and configure special types of files and data, such as registry and INI data, COM servers, Windows services, and. NET assemblies Work with MSI sequences and custom actions Customize your installer's user interface Package your Windows installer for Windows Vista, Windows 7, and later Use the Automation interface to modify your project outside the graphical environment.
Previous InstallShield experience is not required; however, you should be comfortable with: Using Windows Explorer and the command prompt to create and manage files, and run executables Basic Windows terminology e. DLL, Control Panel, etc.
You will also learn about the resources available as you work with InstallShield, including: About the Windows Installer service About Windows Installer installation packages About the Windows Installer installation mechanism About the InstallShield environment Getting help.
In this section, you will learn about: Installation terminology Using the Project Assistant Using the Installation Designer Working with features and components Global product and project data. In this section, you will learn about the different methods for adding files and folders to your installation project, including: Static and dynamic file linking Working with destination folders Best Practice fundamentals "Key" resource usage GUID usage Restarts and the Windows Restart Manager Creating shortcuts Using merge modules and prerequisites.
0コメント