Thanks Rob!
After discussing with our product architecture it's acceptable to have this
FileInUse dialog though it's weird.
I also wander how to add the option into that Dialog because I only refer
that Dialog to my wxs but cannot modify the definition.
UI
DialogRef Id=FilesInUse/
/UI
If that
Hi all,
Can anyone point me towards a good example of an external UI using DTF?
I've been googling for a while and still can't piece it together.
Do I just create a standard WinForms / WPF app and then reference
Microsoft.Deployment.WindowsInstaller? Are there any other references /
attributes
You could run dark on your MSI and copy the dialog out of it.
Rob
On 06/04/2011 08:06, lxy.su...@gmail.com wrote:
Thanks Rob!
After discussing with our product architecture it's acceptable to have this
FileInUse dialog though it's weird.
I also wander how to add the option into that Dialog
Good idea!
Regards!
Sunny
2011/4/6 Rob Hamflett r...@snsys.com
You could run dark on your MSI and copy the dialog out of it.
Rob
On 06/04/2011 08:06, lxy.su...@gmail.com wrote:
Thanks Rob!
After discussing with our product architecture it's acceptable to have
this
FileInUse
Take a look at SharpSetup - http://sharpsetup.eu/ . It may help point you in
the right direction.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated
What is special about your registration that means you can't just heat them,
your code implies it's just regasm?
-Original Message-
From: Asker Brodersen [mailto:asker.broder...@esri.se]
Sent: 06 April 2011 06:41
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] Too many CA:s
If you are following the major upgrade rules
(http://wix.sourceforge.net/manual-wix3/major_upgrade.htm) your 1.1.0.0 dll
should be upgraded to 1.1.0.1. You should note that the component code of
this dll should not have changed. If it's not create a log and see what's
happening.
As to your need
Could anybody tell me what
Directory Id=TARGETDIR Name=SourceDir
Mean, where to keep my setup files and how to create .cab folder
--
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on
Up the theme! )
here:
http://wix.sourceforge.net/releases/3.6.1230.0/history.txt
I have found this string:
MiCarls: Add ListView Tab control support to ThmUtil
does it mean that WIX will be able to support implementing tabs into install
UI? or maybe support already in 3.6.1230.0 version?
A. http://www.tramontana.co.hu/wix/lesson1.php#1.2
B. Not sure what you mean. In a source control system ?
C. http://www.tramontana.co.hu/wix/lesson1.php#1.2 again
-Original Message-
From: swapna.rachako...@thomsonreuters.com
[mailto:swapna.rachako...@thomsonreuters.com]
Sent: 06 April
Hi,
The parameters are stored inside a property that is defined in WIX. How can I
use a static Text and embed the content of a property? I need something like an
escape sequence.
The call i want to make is, PropertyParameters should be replaced by ist
content:
c:\programme\srvany\instsrv.exe
What should be a path for a 'Source' in a File element, I have to add
main executable file for an .msi
--
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable
http://www.tramontana.co.hu/wix/lesson3.php#3.2
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland
Peter Shirtcliffe already pointed you at the tutorial page
(http://www.tramontana.co.hu/wix/lesson1.php#1.2) which explains this in
response to your earlier message. I suggest reading it (and the rest of the
tutorial) as you appear to be struggling with basic fundamentals of Windows
Installer
Hi All,
I found the WIX structure for shortcut entry in MSI.
I need some clarity on the attributes, Directory, WorkingDirectory, Icon and
IconIndex.
What needs to be the value for Directory and WorkingDirectory, if the shortcut
for App1.msi need to be under
Icon Id=ProductIcon.ico SourceFile=$(sys.SOURCEFILEDIR)logo.ico /
Shortcut Id=ProductShortcut Name=$(var.displayName) Description=The
$(var.displayName) application. IconIndex=0 Icon=ProductIcon.ico
Target=[#Main.exe] /
The Shortcut/@Directory attribute says which Start menu folder the shortcut
The ESRIRegasm utility being called generates a registration database (xml
file) for a dll as well as calls RegAsm. It's required for extending the ArcGIS
environment.
Currently I have in place a system where the build msbuild script calls this
utility so the xml files are generated. These
Thanks Pally, I did look at Sharp Setup earlier today. From memory it
didn't use DTF (but maybe I'm wrong). I'm at home now and have just
installed Sharp Setup here but it keeps crashing VS when it generates the
solution.
My current plan is to use Burn from WiX 3.6 to chain .NET and then my
I would like to set up a directory structure under CommonAppDataFolder
that looks something like this:
OrderImport
+- ProviderA
+- Drop
+- History
+- Error
+- ProviderB
+- Drop
+- History
+- Error
and so on... Not much more than this, but
Add a generated registry value to each component and set that as the keypath.
-Original Message-
From: Rune Moberg [mailto:jjfl...@gmail.com]
Sent: 06 April 2011 13:49
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Build a directory structure using
On Wed, Apr 6, 2011 at 3:08 PM, Peter Shirtcliffe pshirtcli...@sdl.com wrote:
Add a generated registry value to each component and set that as the keypath.
Thanks Peter, that did the trick.
--
Rune
--
Xperia(TM) PLAY
Hmm... MSI still is not able to do so.
The ThmUtil is something completely new in WiX 3.6. I assume it is
used for modelling the Burn Bootstrapper UI (Schema for describing
Theme files processsed by thmutil is written in the help). But as it
is very new few information about it and how to use it
Self registration is not usually a good idea, feel free to search the list
for selfreg is evil to see many discussions as to why.
You could also use heat in your build process to make sure the components are
up to date.
If you do want to proceed though I would write a set of CAs that accept a
My understanding is that the 4th position in the version number is not used
by anything when checking version number.
Upgrade, etc ...
I see some version numbers on products use the 4th position as free
formatted.
However when I try to build a package with a number like 1.2.3.123-56-ab-334
I get
No you cannot.
You must use a valid version string for the file versions. MSI requires this
to be able to do a version compare when needed.
You can put this information into the Product version file of the file
assembly, but not into the File Version.
Mat Skildum
-Original Message-
Hi Guys,
I have not found any infomation about using combo box ( the widget where you
can choose one item in a list ) with WIX.
My problem is about dynamic license text localization.
I have seen many post about creating multiple msi, one for each languages. I
have try this, in fact it work
the installer doesn't need to know about the xml files or about COM
registration of the dlls
Really? So what happens when the install fails it has to rollback or the
super unlikely event that someone wants/needs to uninstall your application (or
you force an uninstall during a Major
Amen. I speak to the horrors of SelfReg. I can also speak to the pain of
using Heat to harvest the COM. That's why I wrote a simple little utility
called to put a file system watcher on a directory, run heat and display the
XML
in an XML editor control. We then just copy and paste the XML
Also, take a look at http://support.microsoft.com/kb/905238
If the assembly version remains the same, but the assembly file version
changes, you will need to schedule RemoveExistingProducts after
InstallIntialize
Jacques
On Wed, Apr 6, 2011 at 2:51 AM, David Watson dwat...@sdl.com wrote:
If
Also, take a look at http://support.microsoft.com/kb/905238
If the assembly version remains the same, but the assembly file version
changes, you will need to schedule RemoveExistingProducts after
InstallIntialize
The linked article contradicts the recommendation above to schedule
So if I understand your requirements correctly you want to have a
combobox just for selecting a language for the license agreement?
That should be possible by adding a combobox e.g. on the first
installation scren and afterwards set a property for the selected
language and use this value for the
The scheduling just depends on whether you want to perform a full
uninstall/reinstall and whether or not you want rollback support. Scheduling
after InstallInitialize does a full uninstall without rollback support - but
others can correct me.
The important thing is having the file version set.
Thanks for the responses guys. I'm looking over my setup more and I'll check
out that link.
On Wed, Apr 6, 2011 at 5:51 AM, David Watson dwat...@sdl.com wrote:
If you are following the major upgrade rules
(http://wix.sourceforge.net/manual-wix3/major_upgrade.htm) your 1.1.0.0
dll
should be
On the rollback point, you still get rollback when RemoveExistingProdcts is
after InstallFinalize, but probably not the rollback you'd like because it's
outside of the transacted part of the operation. So the new product installs,
transaction finishes, then the uninstall of the old product
I was also under the impression that FileVersion did *not* contribute to the
naming attributes for a cached assembly. That is the reason I asked.
Phil, you seem to be suggesting that we can also get good behavior (as it
relates to assembly versioning/naming) if we schedule
AFAIK all major upgrade element syntax versions allow Schedule to say where you
want it, afterInstallExecute being the one I mentioned below and the 3rd
bullet here
http://msdn.microsoft.com/en-us/library/aa371197(v=vs.85).aspx which says it
can be sequenced...
Between the InstallExecute
36 matches
Mail list logo
