Yes, during the build the output directory always will be clean for a new
build. So it will be safe to use cab, if it will be found.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Sunday, February 13, 2011 7:42 PM
To: General discussion for Windows Installer
Thanks for quick feedback, Rob!
The bug is here:
https://sourceforge.net/tracker/?func=detailaid=3181941group_id=105970atid=642714
https://sourceforge.net/tracker/?func=detailaid=3181941group_id=105970atid=642714I
would love to contribute one day, when I move from padavan to Jedi ;-)
-- Yan
On
Hello,
Our company is trying to switch over to WIX from InstallShield.
I got our installation program up and running using WIX 3.5.
The problem now is to change the default installation design.
I can't find any documentation relating to this..
Do we really need to design our dialogs from
There's a topic in the help file that installed with Wix, called Customizing
Built-in WixUI Dialog Sets that should tell you what you need to know.
-Original Message-
From: Glenn Terjesen [mailto:glenn.terje...@gmail.com]
Sent: 15 February 2011 09:27
To: wix-users@lists.sourceforge.net
Hello
I appreciate if you stop to copy me in these emails.
Thanks in advance
Milagros
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
To unsubscribe to this mailing list go to...
https://lists.sourceforge.net/lists/listinfo/wix-users
-Original Message-
From: Milagros Moreno Herrera (Intl Vendor) [mailto:v-mim...@microsoft.com]
Sent: 15 February 2011 10:18
To: WiX-users@lists.sourceforge.net
Subject: [WiX-users] wix
Do or do not. There is no try. wink/
On Tue, Feb 15, 2011 at 1:19 AM, Yan Sklyarenko yansklyarenko+...@gmail.com
wrote:
Thanks for quick feedback, Rob!
The bug is here:
https://sourceforge.net/tracker/?func=detailaid=3181941group_id=105970atid=642714
I don't follow the logic there. The cab cache is safe to use only if the
*input* is the same. In other words, if any file that goes into a cabinet
changed then the cabinet containing that file must be recreated.
The output directory is essentially irrelevant to cab cache.
On Tue, Feb 15, 2011 at
I have a similar requirement, I was hoping to find a sample...
Thanks,
Gregg
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, February 14, 2011 11:11 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Using properties
TARGETDIR is the root of your Directory Tree. It essentially represents
the root of the drive you're installing to (as in C: or D: or E: etc).
You shouldn't be trying to use TARGETDIR to install your product in a
standard installation. This is covered in the tutorial (see
Thank you for your reply.
should be more information in the log file about the error.
I have to ask you, which log file is that? Do you mean the event viewer
/ application log?
/Jerra
On 13.2.2011 18:02, Rob Mensching wrote:
If there is a problem in the WiX ServiceConfig custom actions
Hello Sandher/wix-users,
I have been looking for help on this topic but didnt get reply's from anyone
in wix users list. Could you please help me out.
I am new to wix and preparing an MSI for vs2010 web application deployment.
I am done till database config changes. I am facing problems with IIS
Sorry, I wasn't clear.
I am looking for a WIX sample that would allow me to do something like the
following --
Property Id=MyProperty
Value=MyPropertyBasedFolderName /
Directory Id=TARGETDIR Name=SourceDir
Just use INSTALLLOCATION as a Property. You can use Type 51 Custom
Actions to set it e.g.
CustomAction Id=SetInstallLocation Property=INSTALLLOCATION
Value=[MyProperty] /
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
INSTALLLOCATION is automatically a public property you can set from a command
line or with a custom action or from the UI etc.
In fact all directories are msi properties that can be changed, they need to
be public (ALL IN CAPS) if you want to change them from the command line
though. (see Rob's
I've had a need for this in the past. InstallShield for example allows for the
execution of scripts during 'logon' ( validation of the connection, typically
in
the UI sequence ) and has no mechanism to capture a result set. I've written
a
simple data driven DTF custom action that can do
Is there a sample WIX code.
Thanks,
Kavya
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, February 14, 2011 10:15 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Create virtual folder for web applications
Sounds
We do not need different paths for cab cache and output directory. There is no
use cases to store cab cache between builds (when some binary can be changed).
Now our build system manages the build process and the binaries' build, and
installer package creation are different steps for the build
I achieve this by using a CopyFile elememt (a child of the File element).
Basically I copy it to the install location and then copy the file to another
arbitrary location like this:
Component Id=cmpMycomponent Guid=*
Condition
MYDIRPATH
/Condition
Hello,
I would like to use a custom dialog to set properties (like ProductName) that
can be used in subsequent dialogs in a UI (like in the dialog title bar).
However, I'm not sure how to specify when this action should be executed.
Orca shows that InstallUISequence contains the standard
ProductName can not be changed during an install. It can only be transformed
and applied as part of the execution of the installer.
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
Hi,
I'm trying to set a property based on the registry key search. The registry key
as seen in reg editor is
HKLM\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\10.0\VC\VCRedist\x64
I tried 2 combinations -
1. Set win64=no and specify path without explicit Wow6432Node.
Property
Jerra-
Read:
http://support.microsoft.com/kb/223300
you can also say msiexec /i foo.msi /l*v install.log
---
Christopher Painter, Author of Deployment Engineering Blog
Have a hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
- Original Message
BTW, I noticed that you are having your service have a dependency on a database
instance. I'm not sure I would do this.
I would suggest coding the service to spin up it's thread and return from the
OnStart() ( assuming .NET terminology ). Then in the thread I would have a
connection
Although my issue and question isn't wix-specific, it does pertain to
installers in general so I'm hoping someone on this mailing list might
have some suggestions.
I'm working on the installer for my product (using the VisualStudio 2008
Setup Project template) and I've boxed myself into a corner.
We had a similar requirement. This is what we ended up using...
---
?xml version=1.0 encoding=utf-8?
Include xmlns=http://schemas.microsoft.com/wix/2006/wi;
!--
Have to suppress ICE80 warnings for this to work.
--
Property Id=APPFABRIC
RegistrySearch Id=AppFabricRegistry Type=raw
Can I see your user element? What are you specifying as the Domain?
-Original Message-
From: Peter Wilson [mailto:peterwilson...@hotmail.com]
Sent: Monday, February 14, 2011 7:56 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Login failed using User Element, IIS Application
Hi Folks,
I'm just starting to get the ball rolling with WIX and wanted to start off with
the basic visual studio project described in the docs. I follow the steps
(create a forms application project, create a WIX setup project, add the forms
project as a reference to the WIX setup project).
Adding your Forms project as reference to the Wix setup project just
makes the output from the Forms project (exe) available to the Wix
project (var.ProjectName). You still need to tell Wix things like: what
files to include in the MSI that it generates, what kind of UI to use
for dialogs, etc.
Thanks so much for the reply.
I would go ahead with CA for now.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Read-value-from-database-query-tp6024569p6029406.html
Sent from the wix-users mailing list archive at Nabble.com.
Maybe as additional information: A good dialog editor is the
SharpDevelop in a version 3.2.1 or 4.0.1.7090 (available here
http://build.sharpdevelop.net/buildartefacts/) . Older versions of 4.0
have exceptions when editing dialogs.
In general SharpDevelop is able to edit a standalone dialog as
Hello
I'm currently storing the SQL sa password so the database can be uninstalled
later.
RegistryValue Root='HKLM' Key='SOFTWARE\xyz\abcName='SQLPwd'
Value='[SQLPASSWORD]' Type='string' /
Property Id=SQLPASSWORD Value=password
RegistrySearch Id='SqlPwdReg' Key='SOFTWARE\xyz\abc'
I thought I had the virtual directories working. But I was wrong...Well, it is
kind of working but not exactly the way I want it. It is creating virtual
directories but I want to create web applications. So here's what I want to do.
I have some WCF projects which are part of the install and all
As requested:
util:Group Id=grpIIS_IUSRS Name=IIS_IUSRS Domain=[%USERDOMAIN] /
...
util:User Id =$(var.myWindowsUser) CanNotChangePassword=yes
CreateUser=yes Disabled=no Domain=[%USERDOMAIN] FailIfExists=no
LogonAsService=no Name=$(var.myWindowsUser)
Hi
Two things to consider
IIS_USRS is a built in group try not setting the Domain in the group record
(that has worked for me on Win7).I don't know if its relevant but it won't
work on Windows 2003 Server (it uses a different group).
For your user - %USERDOMAIN resolves to the domain of
Or shorter:
SetProperty Id=INSTALLLOCATION Value=[MyProperty] /
On Tue, Feb 15, 2011 at 8:34 AM, Pally Sandher pally.sand...@iesve.comwrote:
Just use INSTALLLOCATION as a Property. You can use Type 51 Custom
Actions to set it e.g.
CustomAction Id=SetInstallLocation
1. Build a new MSI (with the same ProductCode) that uninstalls correctly.
2. msiexec /fv new.msi to recache/reinstall your MSI over the bad MSI.
3. You should now be able to uninstall.
On Tue, Feb 15, 2011 at 11:32 AM, s...@pacaccess.com wrote:
Although my issue and question isn't wix-specific,
Got it!
I thought I had tried different combinations of the XML file but
apparently not. New morning, fresh start.
It works when I remove:
ServiceConfigFailureActions OnInstall=yes
Failure Action=1 Delay=2/
/ServiceConfigFailureActions
Thanks for the logging tip, had no idea such
38 matches
Mail list logo
