5 replies to this topic

[VBScab]

I have made some changes to an MSI, unconnected with Web site creation and now, when it's run on the target, the VD and site get created OK, but the Application doesn't. For the life of me, I cannot see how the changes I've made (which are simply new controls on a dialog box, to select a database file path) can affect these components.

Now, the obvious solution is to remove and re-create these in the GUI (I'm using Wise) but that's going to be labour-intensive. My question is, is there an obvious change I can make to a table or tables to correct this behaviour?

Edited by VBScab, 29 November 2005 - 14:26.

[Stefan Krueger]

Gernerate a verbose log of your install to see what's going on.

[VBScab]

Did that, CA runs OK. I presume there's no error raised because the VD is created succesfully.

[Stefan Krueger]

[VBScab]

When I refer to "application" I'm referring to the app which you can create when adding a VD. I normally leave it to Wise to create the table entries relating to this activity but now I think I need to edit the tables directly.

I tried removing the VDs and even the web site itself but, when I went to add the site back in, it said it already existed.

To recap, I have one working, one not: the latter has simply had 2 controls added to an unrelated dialog. The essentials (i.e. everything except the new controls, properties, etc) of the MSI which is working *look* identical when compared in Wise's Visual Diff, so I'm at my wit's end with this...

[VBScab]

In case someone gets here in future, I thought I'd add the "solution" - I hacked the MS CreateVDirs.VBS (or whatever it's called) from the Platform SDK and ran it via a Custom Action. Result? It always works. Of course, I had to create another CA to remove the VD on uninstall but, again, it always works, as opposed to Wise's lash-up which only does 50% of what it's supposed to i.e it creates the VD but not the application.