deleting shortcut
hi all,
we have a msi here that was created that purely contains three shortcuts. what i thought i could do was simply modify the shortcut in orca, increment the productversion property and run a msiexec.exe /i name.msi REINSTALL=ALL REINSTALLMODE=vomus.
what i'm finding is that it's not removing or modifying the old shortcut, only adding it as a new one.
how do i correct this behaviour?
daniel.
we have a msi here that was created that purely contains three shortcuts. what i thought i could do was simply modify the shortcut in orca, increment the productversion property and run a msiexec.exe /i name.msi REINSTALL=ALL REINSTALLMODE=vomus.
what i'm finding is that it's not removing or modifying the old shortcut, only adding it as a new one.
how do i correct this behaviour?
daniel.
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
You'll need to actually remove them. Use the RemoveFile table.
Posted by:
groulder
13 years ago
thanks mate.
i'm just not sure how to populate the rows in the removefiles table.
i'm just not sure how to populate the rows in the removefiles table.
Posted by:
groulder
13 years ago
think i've worked it out after doing a bit of googling. just not sure on the component column. will have to investigate.
Posted by:
anonymous_9363
13 years ago
You will find it extremely useful to d/l the Windows Installer SDK. One of the principal items therein is MSI.CHM. Hint: check the 'Component' table.
Posted by:
India_Repackaging
13 years ago
Hi Daniel,
I completely agree to Ian's suggestion of reading the MSI.chm. We here call it the Bible as far as packaging is concerned. As far as your query, you can use any component name to add the row in the RemoveFile table. I generally add the name of the component that holds the main executable.
Cheers,
Rajit
I completely agree to Ian's suggestion of reading the MSI.chm. We here call it the Bible as far as packaging is concerned. As far as your query, you can use any component name to add the row in the RemoveFile table. I generally add the name of the component that holds the main executable.
Cheers,
Rajit
Posted by:
anonymous_9363
13 years ago
I generally add the name of the component that holds the main executableI generally don't! :) I prefer to have single components for things like this. It's easy enough to edit the Component table to add a new component. To generate a GUID (components must have a GUID), here's a QAD script. The IE stuff is used merely to copy the GUID to the Clipboard, ready for pasting into the ComponentID cell:
Set objTypeLib = CreateObject("Scriptlet.TypeLib")
strGUID = objTypeLib.Guid
Set objTypeLib = Nothing
Set objIE = CreateObject("InternetExplorer.Application")
objIE.Navigate("about:blank")
objIE.document.parentwindow.clipboardData.SetData "text", strGUID
objIE.Quit
Set objIE = Nothing
Posted by:
AngelD
13 years ago
I disagree; I think it would be a more suitable way to refer to component that has the resource as keypath.
Ian,
Could you explain why you like it "your" way?
Instead of using ORCA, download InstEd then you don't need to generate GUID(s). For columns of "type" GUID InstEd has an option to generate and input the GUID for you.
Ian,
Could you explain why you like it "your" way?
Instead of using ORCA, download InstEd then you don't need to generate GUID(s). For columns of "type" GUID InstEd has an option to generate and input the GUID for you.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.