InstallShield 2010 Evaluator Guide ISP-1600-EG01 3 Chapter 1: Introduction Upgrade Overview. Enhancements to MSBuild support. Automation interface enhancements. Enhancements to the InstallScript language for operating systems. Ability to easily override InstallScript dialog source code in the InstallScript view. Changes to the major and minor version registry entries for the.
![Major Upgrade Installshield 2011 Major Upgrade Installshield 2011](/uploads/1/2/6/5/126510013/337014050.png)
- Live Help
- Components
Component Categories
Component Types
- .NET Components
Component Environments
Component Publishers
- Applications
Application Categories
Application Types
Application Publishers
- Add-ins
Add-in Categories
Add-in Types
Add-in Publishers
- Cloud Services If you have a Cloud Service / API relevant to our global audience of Application Developers and IT Professionals, then get in touch. Every day, customers are searching our web site for software solutions to solve specific IT problems.Join Our Program and start working with us today!
- Brands
Bestselling Brands
It seems this problem is going to be a little more difficult to tackle. When I look at the install log I see a bunch of Action: Null. The problem is this. I reorganized the Features with this release. The problem I was seeing is in the main feature. When I marked the involved file as Always Overwrite, the initial repair went away. But when I check for some files marked in the log with Action: Null, they were still missing. They are in a different feature. I guess they would get repaired when they're hit.
In our old install, everything was under one Feature so everything would have been repaired/replaced/fixed.
Reorganizing the feature shouldn't be a problem as this is a Major Upgrade so what gets placed as new shouldn't matter. It does seem that some previous release information is not being removed properly.
I'm at a loss at the moment. The only thing I can think of doing is placing everything in the Main Feature to test. Each file that triggers a repair would be marked as Always Overwrite and I would have to recompile, reinstall and work through all the problems one at a time. I sure hope Always Overwrite is the way to go.
Something is definitely not right and I have no idea what it could be.
To compound the issue, I'll have to test this on 64 bit also as there are separate features for that. I'll have to ensure that all the components are places properly there as well.
In our old install, everything was under one Feature so everything would have been repaired/replaced/fixed.
Reorganizing the feature shouldn't be a problem as this is a Major Upgrade so what gets placed as new shouldn't matter. It does seem that some previous release information is not being removed properly.
I'm at a loss at the moment. The only thing I can think of doing is placing everything in the Main Feature to test. Each file that triggers a repair would be marked as Always Overwrite and I would have to recompile, reinstall and work through all the problems one at a time. I sure hope Always Overwrite is the way to go.
Something is definitely not right and I have no idea what it could be.
To compound the issue, I'll have to test this on 64 bit also as there are separate features for that. I'll have to ensure that all the components are places properly there as well.