Software Deployment

hi rileyz I have changed the file version that;s not a issue.
1. when I take small update I will not change product version I will add new files in existing features then change the package code & I make a build.
2. when I try to install that build it's not happening file copying action.
3. then once again I tried it's working. I dnt knw how to solve this issue... - perumaldass 9 years ago

Have you looked into the verbose logs yet? It will tell you exactly why its not getting updated. - rileyz 9 years ago

Right sounds like your new to this whole packaging thing. Mentioned that at the start of the question, then its easier for us (: People will still help if your a noob.

if you install the msi via command line with logging... it will produce the log (lol)

msiexec /i <nameof.msi> /qb /l*vx c:\whereyouwantlogfile.log
*The switch is /L*VX just to be clear, run the cmd as admin!

After you have the log, open it up in your fav notepad viewer, recommended notepad++, and look for the file you are trying to update - it will tell you why its not being update. From here you should be able to fix it.

Logging is critical, it will help you out a lot when s* goes wrong. - rileyz 9 years ago

you msi is wrapped up in a .exe. You need to get the MSI itself to use the msiexec cmd. What authoring tool are you using?

Is the MSI/exe a vendor made installer, or yours?? - rileyz 9 years ago

Go Build > Release Wiazard.

Edit the Product Configuration 1, ie dont make a new one. Follow your nose, at the one point it will Say media type, select network image. and after that "uncompressed" - that will give you the msi. - rileyz 9 years ago

http://helpnet.installshield.com/installshield18helplib/MajorMinorSmall.htm **I dont really understand what you are trying to achieve, if your messing around with features, its a major upgrade. **anyway, i always use a major upgrade as it makes life easier for me. If your just updating files in a feature tree -> component, then just update those files and ensure that they are a greater version than those installed. Remember, 1 file per component is the general rule - installshield does a pretty good job of setting this up. If you have config thats needs updating then break that out from AllOtherFiles into its own component. If your that worried about the files not being installed you can always move the RemoveExistingProducts higher in the InstallExec sequence - this will remove the installed product before installing the updated product. ***BUT*** to be honest, this is advance stuff and I dont think you are ready for this, you need someone that knows Packaging, thats with your in person to explain it for your problem. People on here can only help so much, in your case I think someone needs to see your problem to help (or for you have a better basic understanding of Windows Installer technology (Packaging). Good luck, thats it from me, i need to work on my real job! (: - rileyz 9 years ago