Search results for query: *

I think that what you need to do is call the cmd.exe as the executable file, and pass the other filename and switch in as an argument. In which case the exe file would be something like : C:\Windows\System32\cmd.exe the argument would be : /c D:\w2ksp4_da.exe -u Give that a go.

I think that this is the SOURCEDIR property. Should be easy enough to check by getting a DisplayMessage custom action to display the value of the property. From the SDK help file : SourceDir Property The SourceDir property is the root directory containing the source cabinet file or the source...

Ok, sorry - I think that you can more or less ignore this one. The problem that I'm seeing is not what I described above, and it does indeed pick up source files from the property value as it should. The problem I am really seeing is this : One of the files I install is a dll. Before I install...

Hi again, Here's something else I noticed yesterday, and was wondering if anyone else has seen anything similar and can maybe suggest a fix or work-around. I have a Wise Windows 5.21 project that builds two releases. There are a number of dlls included in this project. We were having some...

Hi All, I noticed something when building a few Wise for Windows 5.21 releases yesterday, which could cause me more than a few problems if it re-occurs. I had previously built a project and set a property to hold the root folder of all my source files. I rebuilt the project using the command...

k8e - many thanks. I had a bit of a play with that and it seemed to work like a charm.

Hi all, I'm just starting with Wise for Windows Installer 5.2, new job, new installer. Previously worked a lot with Installshield for Windows (1.5, 2.0) and InstallShield Developer 7.0(ish). The problem that I've encountered already with Wise is setting of dynamic installation locations. This...