J
John M
Hi,
I'm having a problem with shortcut icons not being installed properly.
Installation seems to runs fine except for this single problem.
I have a VS.Net setup project with a shortcut on the start menu pointing to
the program executable. The MSI has two nested MSIs which are COM+ proxies.
In order to get the nested MSIs installed I use Orca to add entries with the
relevant info.
CustomAction
============
UninstallEM 7 EventManagementProxy.MSI REMOVE=ALL
InstallEM 7 EventManagementProxy.MSI REMOTESERVERNAME=[REMOTESERVERNAME]
InstallBB 7 BigBrotherProxy.MSI REMOTESERVERNAME=[REMOTESERVERNAME]
UninstallBB 7 BigBrotherProxy.MSI REMOVE=ALL
InstallExecuteSequence
======================
InstallEM $C__1B142B6D610B4A06BC10CD77780CE57B >2 5601
UninstallEM $C__1B142B6D610B4A06BC10CD77780CE57B <=2 5602
InstallBB $C__1B142B6D610B4A06BC10CD77780CE57B >2 5603
UninstallBB $C__1B142B6D610B4A06BC10CD77780CE57B <=2 5604
Property
========
ALLUSERS 1
After some testing I found that all changes to the MSI except the entries in
InstallExecuteSequence have no affect on the shortcut icon. I.e. I can nest
the MSIs, make changes to the Property and CustomAction tables and the
install will not affect the shortcut icon (of course the nested MSIs do not
run). But when I add the entries to InstallExecuteSequence table the
shortcut icon is the default Windows application icon instead of that which
I have specified.
I posted this in microsoft.public.dotnet.framework.setup originally, but I
got no replies. Does anyone have any clues as to what is causing this.
Thanks,
John
I'm having a problem with shortcut icons not being installed properly.
Installation seems to runs fine except for this single problem.
I have a VS.Net setup project with a shortcut on the start menu pointing to
the program executable. The MSI has two nested MSIs which are COM+ proxies.
In order to get the nested MSIs installed I use Orca to add entries with the
relevant info.
CustomAction
============
UninstallEM 7 EventManagementProxy.MSI REMOVE=ALL
InstallEM 7 EventManagementProxy.MSI REMOTESERVERNAME=[REMOTESERVERNAME]
InstallBB 7 BigBrotherProxy.MSI REMOTESERVERNAME=[REMOTESERVERNAME]
UninstallBB 7 BigBrotherProxy.MSI REMOVE=ALL
InstallExecuteSequence
======================
InstallEM $C__1B142B6D610B4A06BC10CD77780CE57B >2 5601
UninstallEM $C__1B142B6D610B4A06BC10CD77780CE57B <=2 5602
InstallBB $C__1B142B6D610B4A06BC10CD77780CE57B >2 5603
UninstallBB $C__1B142B6D610B4A06BC10CD77780CE57B <=2 5604
Property
========
ALLUSERS 1
After some testing I found that all changes to the MSI except the entries in
InstallExecuteSequence have no affect on the shortcut icon. I.e. I can nest
the MSIs, make changes to the Property and CustomAction tables and the
install will not affect the shortcut icon (of course the nested MSIs do not
run). But when I add the entries to InstallExecuteSequence table the
shortcut icon is the default Windows application icon instead of that which
I have specified.
I posted this in microsoft.public.dotnet.framework.setup originally, but I
got no replies. Does anyone have any clues as to what is causing this.
Thanks,
John