Surendra Katari wrote:
E:\yona\yona\src\Setup\MsiUI\CoreDialogSet.wxs(31): error
CNDL0005: The UI element contains an unexpected child elem
ent 'Publish'.
Which version of WiX are you using? Floating Publish elements were added
several months ago to WiX v3.
--
sig://boB
http://bobs.
Qu, Li wrote:
I thought the .url file itself is the shortcut. Why the content and
shortcut are inconsistent?
Sorry, no idea. It's possible they're cached, I suppose. Try using a
browser other than Internet Explorer as the default. Mozilla Firefox,
for example, supports .url files but does
Jeff MacDuff wrote:
ß in
InstallUISequence Only
It needs to be in InstallExecuteSequence.
Also I looked in the wix help file and I don't see a "Formatted" as a
topic ?
Sorry, I didn't mention -- it's in the Windows SDK (and on MSDN Online),
not WiX.chm.
--
sig://boB
http://bobs.
Magus wrote:
> I don't think your understanding why I am having the problem. My Error
> Dialog does contain all the necessary elements. But it is also Custom Made
> to I control its size and appearance. However after creating the MSI all
> the dialogs that I created are forced to have Control N
I used to work on CBS (that's the team I just quit). Trust me, it is the
latest but it certainly isn't the greatest.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peterson, Joel
Sent: Thursday, November 30, 2006 16:14
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Ne
I saw this while doing some digging as to why PowerShell RTM isn't
available for Vista:
http://blogs.msdn.com/powershell/archive/2006/11/15/windows-powershell-w
indows-vista.aspx
> So what's the difference between the Vista and XP/Server release of
PowerShell? Is it just the installer? Why d
We are hitting the following build error when we tried to add Publish
element. Here is the element we tried to add. What is working with
this. We referred to WixUI library code WixUI_FeatureTree.wxs, it uses
Publish element under UI element.
1
CoreDialogSet.wxs
E:\yona\yona\
We are hitting the following build error when we tried to add Publish
element. Here is the element we tried to add. What is working with
this. We referred to WixUI library code WixUI_FeatureTree.wxs, it uses
Publish element under UI element.
1
CoreDialogSet.wxs
E:\yona\yona\
I am trying to add some RemoveFile/RemoveFolder. I've looking for an example
on the setup work. I have not found an example that has the Property Option
filled out.
Here it what I have
I have a setup project that uses MsiSetProperty(g_hInstall, "Saves",
szLocationof
Thanks for the advice about assemblies earlier. Since everyone seemed to
think we were using assemblies in the wrong way we've once again scaled
back our usage and are no longer trying to use the GAC.
We have some dlls that are used by several different products. Since
different versions of th
This seems not an upgrade specific problem. I did uninstall then new
install using a different port, and the shortcut created by the new
install picked up the port used previously. Something really wired is
that the content of the .url file doesn't match the shortcut. Open the
.url file it has:
Ok I have made the changes (I think) ... but it's still not working:
ß in
InstallUISequence Only
Also I looked in the wix help file and I don't see a "Formatted" as a topic ?
-Jeff
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 30, 2006 9:5
I don't think your understanding why I am having the problem. My Error
Dialog does contain all the necessary elements. But it is also Custom Made
to I control its size and appearance. However after creating the MSI all
the dialogs that I created are forced to have Control Next associated. Thi
Qu, Li wrote:
Actually I tried the following: do RemoveExistingProducts after
InstallFinalize, and do it after InstallValidate. But the URL is not
updated in either case. Is there anything else I should try?
Try adding a RemoveFile element to remove the .url file on uninstall.
MSI won't o
Jeff MacDuff wrote:
2. For the custom action I am using this: Id="GetPublicPicturesFolder" Property="PublicPicturesDir"
Value="[%public%]\Pictures" />
Leave off the trailing % sign. See "Formatted" in the SDK for the syntax
details. The property id also needs to match the directo
I spoke too soon as I cant get this work... here is the syntax I am
using:
1. For the install directory, I am using this:
2. For the custom action I am using this:
3. For the install sequence I am using this:
What I see, is the "property" is set to \pictures
Thank you for your replay.
Actually I tried the following: do RemoveExistingProducts after
InstallFinalize, and do it after InstallValidate. But the URL is not
updated in either case. Is there anything else I should try?
Li
From: Bob Arnson [mailto:[EMA
Oh that's it?
S easy!
From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 29, 2006 5:12 PM
To: Jeff MacDuff
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to specify a envirorment variable dir
Jeff MacDuff wrote:
Sorry could you point me in the
Torsten Rudnick wrote:
> The localization variable !(loc.MaintenanceTypeDlgRepairDisabledText) is
> unknown. Please ensure the variable is defined.
> The localization variable !(loc.MaintenanceTypeDlgRemoveDisabledText) is
> unknown. Please ensure the variable is defined.
>
> These errors occur
aparna wrote:
The idea here was to avoid ICE33 warnings and if I create the registry
keys by using registry/registry values/tags I believe they would cause
ICE33 warnings.
Another thing I noticed was having used TypeLib, Class, AppId and
ProgId tags, the resulting MSI do not have ProgId, Cl
If you right-click on its icon, a context menu will appear. Infected documents
can now be recovered instead of being deleted. The heuristic filter checks mail
for the characteristics of spam.
You can even grab copy another webpage, edit it, and send it out to your
subscribers as your message!
B
Hi,
have a look at the "OriginalDatabase" or the "SourceDir" Windows
Installer-property.
Hth,
Franz
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag
> von Gerald Grininger
> Gesendet: Donnerstag, 30. November 2006 09:04
> An: wix-users@lists
Hi Bob,
The idea here was to avoid ICE33 warnings and if I create the registry keys
by using registry/registry values/tags I believe they would cause ICE33
warnings.
Another thing I noticed was having used TypeLib, Class, AppId and ProgId
tags, the resulting MSI do not have ProgId, Class tables.
I use WiX v3.0.2211.0 and tried to update to v3.0.2315.0. But all
versions above my current one throwing the following errors while using
the Mondo-Dialogs.
The errors are:
The localization variable !(loc.MaintenanceTypeDlgRepairDisabledText) is
unknown. Please ensure the variable is defined.
Geography newsroom subjects to this! Households fertility finance insurance
real, estate health. Tip sheets facts, for, features, minority links decennial
acs! Profile speakers the united. Patterns directors corner economic, surveys
education employment.
October data, highlight changes housing.
Hello,
I need to add licensing functionality to a MSI Package. The package should
be shipped together with a license file which will be evaluated by a custom
action. The problem is that the current directory in the custom action seems
to be the system32 folder. Does anybody has an idea how to
26 matches
Mail list logo
