WISE windows installer - get updated file

Hey guys, I'm new to WISE and created a simple WISE install package for an application.  There is two questions that I have.


This WISE package installs/registers a DLL and installs two config files.  These two config files are stored on a public network drive.  

I want to be able to change the config files and when someone runs the installer on their desktop it will install these updated config files on their system and not the previous ones that seem to be hardcoded into the installer.

Is there some way of doing this?


Is there some way of running a script when someone installs the package.  Basically what I want it to do is if the user has rights to query Active Directory it will query active directory and save a text config file, else it will install the config file mentioned in question 1.


Leo EikelmanDirector, IT and Business DevelopmentAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Leo EikelmanDirector, IT and Business DevelopmentAuthor Commented:
I want to also explicitly add that I don't want to recompile the WISE package to get the update file.


If I understand your question (and subsequent comment) correctly - you want to change the way your created MSI works ... but you don't want to alter the MSI?  If so, I don't think you'll be able to achieve your goal I'm afraid.

It sounds like your MSI (and associated .CAB?) has the two config files embedded in it and expects to install the files on the target system, irrespective of whether the 'correct' config files exist on your shared public drive or not.  You'll not be able to change this behaviour without either re-doing the MSI or, possibly, altering its behaviour with a Transform file.

I'd suggest in this scenario, you either redo the MSI with the latest config file or - if you know the config files will change frequently - consider reengineering your approach to the problem; eg.

a. Let the MSI install the DLL only and ..
b. Get the (frequently changing) config files to the machine in some other manner (login script for instance?)
[c. Alternatively, can the application be configured to look directly at the public drive for its config files anyway?]

Yes there is, but again you'll need to alter the MSI - this is the type of functionality often acheived using Custom Actions within an MSI which will let you run an executable, launch an external/embedded VBScript etc.   In this instance, I suspect a VBScript would be the most appropriate for your needs.

Hope that helps somewhat, but if I've misunderstood your query, please let me know..


Leo EikelmanDirector, IT and Business DevelopmentAuthor Commented:

For Q1.

What you suggested

>>a. Let the MSI install the DLL only and ..
>>b. Get the (frequently changing) config files to the machine in some other manner (login script for instance?)
>>[c. Alternatively, can the application be configured to look directly at the public drive for its config files anyway?]

Essentially, that is what I want it to do.  I want it to install the DLL and then go and get the latests config files from the public drive.  But how would I do that.

For Q2.

If I create a VBScript, how do I make the MSI file run it when it is executed?

Thanks for the help.


Sorry for the delay - been busy in the last few days..!

I'll deal with Q2 first..  I don't use the Wise installer myself, I use InstallShields product, but I suspect the same functionality is available in both under one name or another.    Have a look in the help file for "custom actions".  Generally, you should be able to execute a script your included in your package (or any other valid executable etc.) during the install phase of your package - the VBScript would attempt to query your AD and, if appropriate, copy the config files from your public directory.   The following might help:  http://www.appdeploy.com/articles/msi_kix/index4.asp

Q1.. If you add a VBScript to your MSI, then you'll end up with the 'uptodate' config files *at the time of the MSI being installed*.  However, if you change the config files on your public directory, the MSI will not update them from there (it's done its job - installing the DLL..) - you'll really need to put something in place to keep the local and public directory config files in sync - you could acheive this with a VBScript called from your login scripts perhaps?



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Leo EikelmanDirector, IT and Business DevelopmentAuthor Commented:
Thanks for the response.  We decided to go a different direction but I'll still give u the points for your suggestions.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.