Here is the problem I'm trying to get around. A typical deployment scenario of our applications is basically nothing more than copying the same set of files (an EXE and a preset number of DLL's) from the same network location to user machines. Files names will be the same at every deployment. The important thing is, however, that the files themselves are going to be different since they are regenerated every time to include the latest code changes done to the apps.
I successfully built and tested an MSI that does the job. Now when I change one or more of my files and rerun the same MSI, it copies the old files, namely those that were used at the time of creation the MSI. This seems to be a major obstacle because we would have to recreate our MSI every time as well to "refresh" the files that come with it (get the newest files "embedded" into it). But we want to completely automate it.
What we would like to have is an MSI that would go to where our files are and "grab" the ones that are currently there. Like I said, the number of these files, their names and location will likely never change. Is there a way to accomplish this?
MSI factory doesn't seem to have a setting that would tell an installer to get fresh files as oppose to copying those that got built into it. I also tried bootstrapping but that did not help either. I'm probably missing something very simple.
Any ideas will be highly appreciated. Many thanks!
Leon, the developer