Kelly Summerlin wrote:
> So it sounds like here that I should have separate GUIDs for 32-bit and
> 64-bit definitions even though the assemblies that are being
> deployed are exactly the same. If this is the case, then I can
> understand the need for separate GUIDs, but it sure makes maintainin
John Calcote wrote:
> Hi,
>
> Can anyone tell me what the following error message from the Orca
> Validator means:
>
> ICE43 ERROR Component PROGUID_comp has non-advertised shortcuts. It
> should use a registry key under HKCU as its KeyPath, not a file.
>
> ??
>
I tend to ignore that one. It
Derek Cicerone wrote:
> That means that the component needs to have a registry key under HKCU as its
> keypath. This supports installation of per-user shortcuts for a per-machine
> installation.
I don't see why anyone would ever want to do this - put per user shortcuts in
per user installations
Foster, Richard - PAL wrote:
> Tony,
>
> One scenario we have in our systems is that our customers may want
> *some* users to have access to all the components, but other users to
> only have access to certain items.
I guess it's the line where you limit your support - if one of our customers
wa
Jeremy Farrell wrote:
> I agree totally. As far as I'm concerned this is a useful feature. I
> want to be sure the ProductCode changes every time, to ensure that it is
> impossible to do anything other than major upgrades. This may be an
> unusual requirement, but it's a valid one and I shouldn'
Derek Cicerone wrote:
> Non-advertised shortcuts require dummy HKCU keypaths in their components
> – do you have those? (This is one of many mistakes ICE validation catches)
>
The OP is using ALLUSERS=1 so that would make the problem worse, not
better (modifying HKCU in ALLUSERS would mean that
Magus wrote:
> While creating a dialog box in Win32 I used the RichEdit2.0 control, and it
> runs fine until I try to call my .dll dialog in Wix. It seems it doesn't
> know what the wnd class is for richedit. Anyone ever come across tis
> problem?
Have you remembered to call called InitCommon
Standa Kunc wrote:
> ACTION: SharedFile: "C:\WINNT\system32\COMDLG32.OCX"
> (File was now found or had older version -- new file was copied)
Avoid modifying system32. Definately don't 'upgrade' anything found there -
you have no idea what other applications you're breaking whilst attempting to
Standa Kunc wrote:
> Where can I get msm file for olepro32.dll? Thank you.
>
You don't need one it exists on the base install of windows.
Tony
-
Using Tomcat but need to do more? Need to support web services, security?
Get
Tiago Silva wrote:
> 1. How do I produce a double click install to install the upgrade? The
> upgrade that i've playing in tutorial gives me a "Product already
> installed" message when I install it by double clicking the msi file.
> I'm using a minor upgrade, i.e., the same ProductID and different
Bob Arnson wrote:
> so you won't be able to do major upgrades between 1.0.0.40 and 1.0.0.41.
I think you meant minor upgrades there.
Major upgrades uninstall the old product first so there isn't any issue
with version numbers.
Tony
---
11 matches
Mail list logo
