Hi Richard,
Any Suggestions?
Thanks
Amit
On Mon, Oct 20, 2008 at 10:14 PM, Amit Shrivastav [EMAIL PROTECTED]wrote:
that custom action is present in old as well as new assembly. and also I am
putting assmblies in the GAC as well in the upgrade scenario.
On Mon, Oct 20, 2008 at 9:14 PM,
First I feel your pain I am doing something similar. The way I see it,
WiX installs the application, the bootstrapper is for prerequisites that
may or may not be on your destination PC. Yes you could use NSIS for all
of this but you will get a better application installer using Windows
Installer
I'm running into some problems with XmlConfig. I've found that the following
does not work:
util:XmlConfig Id=CreateDummyElement
File=[SOMEFILE]
Action=create
ElementPath=/startingPath
Name=Dummy
Node=element
Do you have RemoveExistingProducts scheduled?
Rob
Libor wrote:
Hi guys,
I am quite new into the msi business, and I can't figure this out:
I have two versions of my project, and of course I want to remove the
previous version when a new version is installed. I used wix for my
Hi Brian,
Which version are you using? I remember that once upon a time, ElementPath
required a XmlConfig Id:
Therefore, using
ElementPath=CreateDummyElement is valid.
Rgrds,
Eitan
-Original Message-
From: Brian Rogers [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 9:18
Howdy,
In my installer I should show licensing dialog at the end of installation.
If the product is removed, the licensing dialog should not be shown though
and user exit dialog should be shown instead. I try to use conditions like
below:
InstallUISequence
Show Dialog=LicensingDlg
Thanks Rob.
Sorry for being a bit blatant - I was feeling a bit frustrated. It's hard to
justify the spending of so much time to build an installer that was almost
done in NSIS :-).
Anyway, I found a good solution. I still use the Visual Studio Bootstrapper,
but added a GenerateBootstrapper (in
Thanks for the answer, but it dosn't work.
I used MsiGetMode(hInstaller, MSIRUNMODE_REBOOTATEND); but it is allways
false. Also when after the installation the messagebox for restart appear.
I call my custom action deffered before InstallFiles and before
InstallFinalize. Both the same...
Maybe there is a
better property than $(TargetPath) (is there?), but for now I just hardcode
the msi's name.
$(TargetFileName) ?
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the
Your second try is almost correct. You need to add the following to your
code however:
InstallExecuteSequence
RemoveExistingProducts After=InstallInitialize /
/InstallExecuteSequence
Otherwise, as you've noticed, the existing version is not uninstalled
before the new one is
Hi,
Thanks a lot for your suggestions.
Could you please let me know how to implement the first one (.reg files)
as you suggested.
Thanks again.
Regards,
SivaKrishna Kalvagadda,
201-671-5552.
-Original Message-
From: Richard [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2008 6:42
.reg: Don't use the .reg file; instead put the registry
values in the .reg file into a component and install the component.
Thanks a lot for your suggestions.
Could you please let me know how to implement the first one
(.reg files) as you suggested.
You need to create a component and in
Correction to the GenerateBootstrapper elements, using properties:
GenerateBootstrapper ApplicationFile=$(TargetFileName)
ApplicationName=$(TargetName)
CopyComponents=true BootstrapperItems=@(BootstrapperFile)
ComponentsLocation=Relative
OutputPath=$(OutputPath)\pt-BR
Hi John,
Thanks a lot, I got the below one.
Could also help me in setting up the IUSR_ on IIS.
Regards,
SivaKrishna Kalvagadda,
201-671-5552.
-Original Message-
From: John Hall [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 9:49 AM
To: General discussion for Windows
Hi All,
Could anyone help to create user groups and users under that using WIX.
Thanks.
Regards,
SivaKrishna Kalvagadda,
201-671-5552.
This message w/attachments (message) may be privileged, confidential or
proprietary, and if you are
I'm using WiX 3.0.4513.0.
##
$_='^#(/||/@[EMAIL PROTECTED]@:^[-['^;@@@\\])@..
{)/];)^{;$,+=(++$,);$_.=$,;`$_`;
-Original Message-
From: Eitan Behar [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 1:33 AM
To: 'General discussion for Windows
OK, I think I understand what's going on here. The reason a certificate
looked like it was duplicated was that the same cert existed in multiple
physical stores, which appeared as the same logical store in the mmc.
If the certificate the installer was trying to add already existed in
the Group
Wow, nice analysis. Is there a bug open on this issue right now? If not, can
you open one and I'll try to get this change in Thursday night for Friday's
build.
-Original Message-
From: Chris Bardon [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 07:47
To: General discussion
Hi, i've been a bit distracted so got half way through trying to implement
this..
I'm installing an IE plugin so would like to prompt the user to get them to
restart IE (or at least ask if they want to) and i'm having a few problems
I can use the closeApplication custom action to set a
I am able to create the user and map it to Domain\Group. Is there any
way to create new domain\group and map the user to it?
Thanks
Regards,
SivaKrishna Kalvagadda,
201-671-5552.
-Original Message-
From: Kalvagadda, SivaKrishna (MLX Technology)
Sent: Tuesday, October 21, 2008 10:27 AM
My guess is that your performance counters are being uninstalled because the
condition is something like REMOVE=ALL. If you don't want the uninstall
custom action to run from your old uninstall if it's upgrading than that
uninstall needs to add the condition AND NOT UPGRADINGPRODUCTCODE.
Phil
I'm following Peter Marcu's Patching something you didn't build with WiX using
WiX to try to patch my existing MSI that was built with WiX, but built with a
version before WixPDB's.
The error text is:
C:\dev\flamingo\2.0\diff.wixmst : error PYRO0104 : Not a valid output file;
detail: Invalid
Don't think the Group element supports that today.
-Original Message-
From: Kalvagadda, SivaKrishna (MLX Technology) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 09:46
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Creating Users and User
Thanks, I've opened a bug (number 2184946).
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 12:24 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Certificate install to local machine
failswithcode
Is there any other way to create Group?
Regards,
SivaKrishna Kalvagadda,
201-671-5552.
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 1:09 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creating
Custom action?
Kalvagadda, SivaKrishna (MLX Technology) wrote:
Is there any other way to create Group?
Regards,
SivaKrishna Kalvagadda,
201-671-5552.
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 21, 2008 1:09 PM
To: General
Hi All,
How do you grant permissions to a folder for a specific user if the user
happens to be the built in Network Service account?
I have tried:
Component Id=AssignDataDirectoryPermissionsGeneric
Guid=5A9D6D2B-CBA0-4E4C-8935-FACA2446256E
CreateFolder Directory=DataDirectory
In article [EMAIL PROTECTED],
John Hall [EMAIL PROTECTED] writes:
.reg: Don't use the .reg file; instead put the registry
values in the .reg file into a component and install the component.
Thanks a lot for your suggestions.
Could you please let me know how to implement the
Here is code from an installer I have that works for me:
Component Id=CID_Logs Guid={837A1B74-98C9-4042-B51D-58F38448CE46}
Location=local DiskId=1
CreateFolder
Permission GenericAll=yes User=Administrators /
Permission GenericRead=yes GenericWrite=yes User=Network Service /
/CreateFolder
WinRAR! I've been using WinRAR for years as my main compressed archive
viewer, but only just recently discovered it has support for creating
self-extracting archives (SFX it calls them) as well! Not only that but it's
by far the best out of all of the ones I've tried.
Namely, it does everything
I have an Xml file I need to put in another application file, write some xml
to it and run it with that 3rd party application.
Sequence of events:
1. Write Xml to file
2. Get the Directory/Folder where the 3rd party application is sitting from
win.ini
3. Copy Xml file to 3rd party app folder
Logan,
Thanks for the tip.
You can also use 7-zip. It does that for free.
It even has a special SFx for windows installation and you can configure the
dialogs messages (if needed).
But doesn't provide options for configuring icons and such.
-Original Message-
From: chaiguy1337
John Lister wrote:
I've tried to use the Description property of CloseApplication to display a
message, but that doesn't seem to work. I've also tried to schedule another
CloseApplication to occur at the end of the install based on the value of my
property:
You need to make the
tomer saban wrote:
I want to know what is the influence (if any) of the warning :
Warning 7 The File/@AssemblyManifest attribute's value,
'NiceApplications.SystemAdministrator.IntegrationsPlugin.RejectedDevices.dll',
is too long for an identifier. Standard identifiers are 72 characters long
Neil Sleightholm wrote:
I am looking to create a VM for building the WiX v3 source, I currently
doing it on my main PC running Vista but I am wondering what other
people use. Is Vista a good base or would you recommend something else,
XP seems to be easier to manage but would Windows Server
Nghi Nguyen (CSD) wrote:
I notice that the only way to do something of what I required above is
CloseApplication. However, I found no example on how to use this, and I
don't know how to get a dialog to display in conjunction with this feature.
See the source code for the WiX setup
Sergey Abakumoff wrote:
Show Dialog=ExitDlg OnExit=success
![CDATA[REMOVE = ALL)]]
/Show
However, with this line LicensingDlg isn't shown during installation and
ExitDlg isn't shown during removing the product.
You can't have multiple success dialogs, per the MSI SDK
Hi,
I'm helping our dev group develop a standards doc for WiX development. Does
anyone know of a good pointer to share on best practices or suggested standards?
Thanks!
-greg
-
This SF.Net email is sponsored by the Moblin
John Lister wrote:
I've tried to use the Description property of CloseApplication to display
a message, but that doesn't seem to work. I've also tried to schedule
another CloseApplication to occur at the end of the install based on the
value of my property:
You need to make the property
I've got an issue with an old install on a system that we are upgrading.
The issue is that one of the custom actions is depending on a property that is
only available during a UI install and when an upgrade is performed the
previous install is removed silently and the custom action fails
Hi, I'm trying to create a patch for two products, let's say Foo and Bar. I
wanted to know how I should go about creating a patch for them? I have a .wxs
file which I'm using as a template. It has a single UpgradeImage tag which
picks out the upgrade and target MSI's. Should I simply add a
In article [EMAIL PROTECTED],
Dan Hoeger [EMAIL PROTECTED] writes:
The issue is that one of the custom actions is depending on a property
that i s only available during a UI install and when an upgrade is
performed the previ ous install is removed silently and the custom action
fails
Hello again,
I've been tearing my hair out over the last week trying (but failing) to
register a .Net assembly TypeLib in WiX 3 (so apologies if I sound
frustrated).
Heat only got half way - and even then I had to alter the output somewhat in
order to get it to do the equivalent registry
I had a problem this morning with XMLConfig. Somebody also had a similar
problem.
Here is the code to add a value to an element (not an attribute):
util:XmlConfig Id=ViewpointButtonPicture
File=[INSTALLLOCATION]aero.justify.xml Action=create
ElementPath=//[EMAIL
1. Dark can convert an existing MSI into .wxs files. You may be able to use
the -f switch to highly fragment everything and use the output as-is. It
sounds like there is just a lot of registration that is necessary for these
assemblies.
2. If you can, please file detailed bugs on heat.exe
The WiX help file for WiX 3.0 has a bunch of how tos that document best
practices for various tasks. Most of them will likely apply to WiX 2.0 as well.
When you are done with your best practices doc I'd love to see a copy :)
Neil
-Original Message-
From: Greg Silin [mailto:[EMAIL
Thanks. I decided to go for Windows 2008 (mainly because I haven't used
it yet). I have found the WiX build documentation is a bit thin so I am
documenting the process as I go and will post a blog entry when I have
it working.
Neil
-Original Message-
From: Bob Arnson [mailto:[EMAIL
Hi,
here is a small sample which defines a ComponentGroup and uses this group
in two features:
---
?xml version=1.0?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
Product Id=12345678-1234-1234-1234-123456789012 Name=Test Package
Language=1033
I have found a solution to the error: src\dtf\tools\sfxca\precomp.h(32)
: fatal error C1083: Cannot open type library file: 'mscorlib.tlb': No
such file or directory.
If you add C:\Windows\Microsoft.NET\Framework\v2.0.50727 to the path
before running the build it should fix it.
Neil
Also be prepared to give your build service account full admin rights.
See this thread for some details:
http://social.msdn.microsoft.com/Forums/en-US/tfsbuild/thread/525e9b71-d
267-4177-880c-957df9c92fd4.
-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent:
Hi,
I am trying to upgrade my installer using property *UPGRADINGPRODUCTCODE. *In
the previous MSI it was not there. now In the latest version i.e. upgraded
msi contains that version. I have an custom action in original msi which
execute at the time of uninstallation. In the upgrade msi i dont
If you don't want the original msi to execute the custom action when being
uninstalled via major upgrade, you need the condition of NOT
UPGRADINGPRODUCTCODE to be in the original msi. It's not clear to me if you
have that condition in the original msi or the second msi.
-Original
i have placed that in the second msi(upgraded msi). but it is not working
though :(
thanks
amit
On Tue, Oct 21, 2008 at 4:32 PM, Ian Elliott (Excell Data Corporation)
[EMAIL PROTECTED] wrote:
If you don't want the original msi to execute the custom action when being
uninstalled via major
original msi doen not contain that condition NOT UPGRADINGPRODUCTCODE.
Is this mandatory? Is there any other way so that i can stop executing that
custom action in the uninstallation through Major upgrade.
On Tue, Oct 21, 2008 at 4:57 PM, Amit Shrivastav [EMAIL PROTECTED]wrote:
i have placed
If you schedule RemoveExistingProduct *after* InstallFinalize, major upgrade
will touch only components where keypath is different. If you did not change
your performance counters, they should not be uninstalled. Component will be
upgraded regardless of UPGRADINGPRODUCTCODE if keypath is
That uninstall for the older version of the product is already out there on the
systems where the product is installed. You can't change its behavior unless
you apply a patch or other minor upgrade.
You may be able to correct your problem with this sequence towards the end of
your
I am trying to execute the custom action which was also in the previous msi
and was working fine. In the upgraded msi when i runs it throws the
following error:
*Error 1001. The installation failed, and the rollback has been performed.
-- Could not find a part of the path
I'm getting this error in my setup -
ExecFirewallExceptions: Installing firewall exception
ExecFirewallExceptions: Failed to connect to Windows Firewall
Error 25580. Cannot connect to Windows Firewall. (-2147023143 )
.
.
.
Error 0x800706d9: failed to get firewall profile
Has anyone
no alex I did not touch anything about the performance counters in the new
upgraded msi even keypath is also same. but still it is uninstalling it. :(
Can you give some other idea to implement this.
On Tue, Oct 21, 2008 at 5:29 PM, Alexander Shevchuk
[EMAIL PROTECTED] wrote:
If you schedule
No i tried that also. but still it is not working. that custom action is
throwing error.
On Tue, Oct 21, 2008 at 5:30 PM, Wilson, Phil [EMAIL PROTECTED]wrote:
That uninstall for the older version of the product is already out there on
the systems where the product is installed. You can't
*No i tried that also. but still it is not working. that custom action is
throwing error. *
*RemoveExistingProducts action sequenced incorrectly. i placed this after
PublishProduct before installFinalise.*
On Tue, Oct 21, 2008 at 5:59 PM, Amit Shrivastav [EMAIL PROTECTED]wrote:
No i tried
Hi,
I am running candle command and I have used sql component in my WXS file. Due
to this I am using -ext switch and after that giving the path of
'WixSqlExtension.dll'. But I am getting error CNDL0103 error. If I am working
directly in Wix bin directory and giving only 'WixSqlExtension.dll'
I think you answered your own question. I imagine stopping the firewall
service makes it so you can't configure it in this way. Perhaps you can add a
ServiceControl element to ensure the firewall service is started (although I'm
not sure it would be guaranteed to be sequenced at the right
Obviously if you're in the Bin folder it will find the file because that
file is in the Bin folder however it doesn't work when the current
directory is not the Bin folder perhaps you can add the path to the -ext
switch?
e.g. -ext C:\Program Files\Windows Installer XML
Thanks Ian, but I need to add to permissions on the directory rather
than reset them altogether.
Does anyone else know what values I would need to use for user and
domain in the PermissionEx element to get permissions assigned to that
directory for NT AUTHORITY\NETWORK SERVICE?
Just as an FYI, I
Wow, AutoIt is really great! I'm totally loving it. It's a simple, easy to
use syntax and it's quite sophisticated. Compiles to a native app, very
small footprint. I've got a nice little custom bootstrapper now, combined
with my WinRAR self-extractor and WiX installer, and this is shaping up to
[EMAIL PROTECTED] wrote:
Obviously if you're in the Bin folder it will find the file because that
file is in the Bin folder however it doesn't work when the current
directory is not the Bin folder perhaps you can add the path to the -ext
switch?
e.g. -ext C:\Program Files\Windows
Nic Barden wrote:
Could this issue be something I may have introduced by adding my own
Publish Dialog=CustomizeDlg Control=Next ... / declarations, somehow
removing the existing functionality?
I don't think it would affect it, but does it work as you'd expect if
you drop the floating
Brian Rogers wrote:
I think you answered your own question. I imagine stopping the firewall
service makes it so you can't configure it in this way. Perhaps you can add
a ServiceControl element to ensure the firewall service is started (although
I'm not sure it would be guaranteed to be
The problem that we're hitting is that it appears that the WiX custom
action is throwing a dialog - any way to suppress that dialog?
Wendell
On Tue, Oct 21, 2008 at 9:08 PM, Bob Arnson [EMAIL PROTECTED] wrote:
Brian Rogers wrote:
I think you answered your own question. I imagine stopping the
I am running candle command and I have used sql component in my WXS file. Due
to this I am using -ext switch and after that giving the path of
'WixSqlExtension.dll'. But I am getting error CNDL0103 error. If I am working
directly in Wix bin directory and giving only 'WixSqlExtension.dll'
Hello Amy,
I actually use [ComputerName]\iis_wpg this is IIS Working Process Group of
which network service is a member. Although that said, this group only exists
if IIS is an installed windows component. This covers, system, network
service, local service and I think Aspnet.
Michael
72 matches
Mail list logo
