mahantesh.desai@infovista.com asked a question.
Hello Team,
We are experiencing an issue with our InstallShield project after adding new files to our repository. Our application is packaged using InstallShield, and all builds run through Azure DevOps, with source hosted in Azure Git Repos.
Recently, we added several new DLL and MDL files to the repo. Initially, these files were blocked by our
.gitignore
rules. We resolved this by overriding the
.gitignore
settings and successfully committed the files.
However, after updating the
.ism
project to include these new files and running the Azure DevOps build, the final InstallShield installer does not contain these newly added files. The build completes successfully, but the resulting package excludes the files despite being present in source control and referenced in the
.ism
.
@mahantesh.desai@infovista.com : Is your files are linked to the project ism file in a static linking or dynamic linking, if its a dynamic linking once you copy your new files to the same dynamic linked path those new files will be added to the ism and included in to your final setup.exe
if your files are static linked, then you need to link your new files to project ism file and then sync to your git to the same path, so that the new files will be included in your project ism file and the final installer setup.exe