The simple way to resolve is to use 2 different GUID for different
components...
-hansen
Sergey Abakumoff wrote:
>
> Yeah, after some more testing it seems that adding the Name attributes for
> the files that represent the satellite assemblies crashes the installer.
> I.e. I do the following:
f your transitive components? What your shortcuts
> point to - file or folder? Are shortcuts in the same component as files
> they point to (providing that they point to files, of course)? Are you
> sure that old components are uninstalled?
>
> Alex
>
>
> -----Original Mes
...haha
Good luck guys who have similar problems =)
-Tony
shenlong wrote:
>
> Hi Michael,
>
> Issue: On upgrading product, shortcut name Product 5.1 is installed, but
> shortcut name of 5.0 is not removed during major upgrade.
>
> I've followed Alex's guideline
the old shortcut was not removed. My guess is that something is
> breaking on your uninstall of the old version (not getting completely
> uninstalled). Check your logs for hints.
>
> shenlong wrote:
>> Hello guys,
>>
>> I'm using the SoftwareName and VersionNo to
Hello guys,
I'm using the SoftwareName and VersionNo to for the shortcut name on desktop
and Program Menu. As you can see, VersionNo is variable,i.e. it changes with
new builds.
For example, Product 5.0. If I upgrade to Product 5.1, the desktop and
Program Menu creates new icons shortcut called
5 matches
Mail list logo