I use ServiceInstall and ServiceControl and noticed that if my service
failed to start [a bug in my code], then the install failed.
Is there a means to try to start the service and have it install even if it
fails to start?
P.S. Also, fwiw, I noticed that if I used two ServiceControl
Hallo!
We are building our complete software using ms-build.
For building the setup, which consist of different projects, we created
a solution combining all these projects.
Out of the build process I need to build this solution twice with
different settings and ideally with different
Hi Wendell,
I had looked at that web page, but it never dawned on me it would be that
simple.
I thought it was a special property like the other PropertyRef ones, but when I
tried that nothing happened.
Thanks for the clarification.
Dominique.
-Original Message-
From: Wendell Joost
Have you tried using CopyFile Element ??
http://wix.sourceforge.net/manual-wix2/wix_xsd_copyfile.htm
-Original Message-
From: Dave Kolb [mailto:d...@dotnetcodeslingers.com]
Sent: Tuesday, October 13, 2009 9:47 AM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re:
There are several ways to do it apparent, but this is what works for
me...
Set up your control up like this...
Control Id=CmbSQLServerInstance Property=SQLSERVERINSTANCE
Type=ComboBox Height=15 Width=140 X=14 Y=93 Text=Ppphhh
ComboList=yes ToolTip=The instance of SQL Server you would like to
Is anyone able to confirm my suspicions, or suggest an alternative method for
influencing the feature options?
--
View this message in context:
http://n2.nabble.com/Setting-feature-options-tp3788261p3815424.html
Sent from the wix-users mailing list archive at Nabble.com.
Hi ,
Please guide me to create a web setup (.msi).
I have a .msm file created in visual studio merge module which basically
does all the work.
1.It creates a virtual directory and deploys the web application.
2.It creates various performance counters and installs it.
I want to refer it into a
Hi WiX users,
I am seeking advice how I can accomplish the following:
I found out how to sequence custom actions after InstallFinalize. For my
installation requirements I need a finer degree of control when custom
actions are run, particularily I am seeking for a way to execute a custom
action
Hello,
if anyone is interested, there's a spelling error in the german
translation file in the source-package of wix.
Index: WixUI_de-de.wxl
===
--- WixUI_de-de.wxl (Revision 90)
+++ WixUI_de-de.wxl (Revision 91)
@@ -1,4
Shortcut names are exposed to users on XP systems and may be exposed to them
on Vista systems, depending on whether they have had a native resource dll
string table entry assigned to them. The windows shell which is responsible
for showing the start menu is either all or mostly native code, the
To reduce reboot prompts many of us set @Stop to both.
Windows Installer assumes that if you want the service started during the
installation, it is a failure if it doesn't. It uses the built-in action
StartServices, which can't be redefined to ignore (all you can do is
condition it, which isn't
I haven't tested it, but what happens if you set @InstallDefault='local'?
-Original Message-
From: Gareth [mailto:gmor...@serif.com]
Sent: Tuesday, October 13, 2009 4:01 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Setting feature options
Is anyone able to confirm my
Not sure, but InstallUtil* is Self-Reg (aka evil). Visual Studio's setup
projects do several things that make deployment easier that invariably
cause headaches later on when you have to service/maintain those setups
(including broken upgrades, orphaned resources, failed removals, etc.).
Sequencing is the order in which the actions are queued to run. Conditions
is the decision to run or not run any arbitrary action.
You need to look at conditional syntax and set the condition of your action.
However, there is an issue with what you describe you need:
In the sequence between
Please file a bug.
-Original Message-
From: Thorsten Schöning [mailto:tschoen...@am-soft.de]
Sent: Tuesday, October 13, 2009 5:20 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] error in german wxl file
Hello,
if anyone is interested, there's a
The wixlib looks like exactly what I need--thank you for pointing me in that
direction. I *almost* have it working, except I can't figure out what to use
for the Directory elements in the common wxs file. The components in the wxs
file will be installed in different locations in the stand-alone
Guten Tag Blair,
am Dienstag, 13. Oktober 2009 um 05:57 schrieben Sie:
And changed it to this:
XmlFile Id=SignWrapper_XMLSettings_PDF1
File=[SignWrapper_RootDir]signwrapper.xml Action=setValue Value=0
ElementPath=//signwrapper/BEFDE7B3-54DB-419e-BB46-5FA8CE997AD5/spezial/disa
The problem I'm having with this is for the accept license checkbox of the
Minimal UI. It's really awkward to make that UI not look ugly.
The external UI is interesting. One way that seems reasonable would be for
an external UI in a bootstrapper to come up with values for all sorts of
public
Hi.
I can successfully deploy an application that includes a web application
among others (thanks to this list) like this:
!-- Inside a component --
iis:WebVirtualDir Id=SomeWebApp Alias=SomeAlias
Directory=INSTALLLOCATION WebSite=DefaultWebSite
iis:WebApplication Id=SomeWebApp Name=SomeName /
Hi Ben,
I have resolved all install/uninstall issues with websites in IIS with
the code below. By storing properties in registry and reading them
back, all works fine.
I have included the port, description (name), hostheader value and IP
address as registry values. This allows me to have
Blair thanks but I have to confess to not understanding that explanation at
all. What would be such a case that an XP or Vista user saw a short name
instead of the NTFS name? - Dave
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Tuesday, October 13, 2009 9:22 AM
To:
Be careful there. A short name (8.3 convention) is different than a
Shortcut, which is what your subject line implies.
-Original Message-
From: Dave Kolb [mailto:d...@dotnetcodeslingers.com]
Sent: Tuesday, October 13, 2009 8:56 AM
To: 'General discussion for Windows Installer XML
Hi Craig.
Thanks for the fast response! Actually I found your code/the nabble link
below already before posting to this list, I just don't understand if that
helps me. Probably I'm just too new or not able to express my problem in a
good way:
I install on machines where a default site is present
Thanks Blair. In that case, I think I will start the service with a CA. What
would be the proper sequence point to do this? Thanks, Dave
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Tuesday, October 13, 2009 9:27 AM
To: 'General discussion for Windows Installer XML
We had something like this but managed to catch it after it had gone to only
one customer. The
installer we gave them had a condition that prevented it from being
uninstalled. I had to install
it locally and find the cached copy. You can either do this by searching the
Windows folder or
Thanks Chad as I did not notice I said that. I definitely mean a short
name or 8.3 name. I would just as soon not clutter my .wxs file with them
if I don't need them and so am wondering on XP forward in what cases a user
would see one of the auto generated short names if I did not specify them
and
When a product is installed, are we supposed to have our .wxs file register
an entry into HKLM\Software\[Company]\[Product] ourselves or is this
something the .msi installer is supposed to do for us somehow? I looked at
my old .msi files build with VS2008 before wix and did not see any special
Hi Ben,
I see. I'm doing just the opposite. Installing new website/app, but
leaving default alone. Not sure how to install/uninstall just the app
like you need. Sorry for the confusion and sorry I don't have any good
info on that one. If I run across it, I'll be sure to share.
Thx, Craig
Nevermind on the ARP stuff. I defined the values and they just work! Am
still wondering what is the proper thing to do in regards to registering the
install of the product though. Thanks, Dave
From: Dave Kolb [mailto:d...@dotnetcodeslingers.com]
Sent: Tuesday, October 13, 2009 1:24 PM
To:
An 8.3 filename (also called a short filename or SFN) is a filename
convention used by old versions of DOS and versions of Microsoft Windows
prior to Windows 95 and Windows NT 3.51. It is also used in modern
Microsoft operating systems as an alternate filename to the long
filename for
in the wix 3.5 release work is a file | new | project | wix | patch project
template going to eventually get included?
--
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event
Thanks Chad. In spite of calling it a shortcut, I know what a SFN is since
working on PCs from the very first version of DOS 1.0, but am wondering why
I might want to have anything meaningful for a short name nowadays. Since
these names would be for my program files I'd really rather not any
There are still filesystems that Windows can use that are short name only.
Brant Gurganus
http://gurganus.name/brant
On Tue, Oct 13, 2009 at 2:37 PM, Dave Kolb d...@dotnetcodeslingers.com wrote:
Thanks Chad. In spite of calling it a shortcut, I know what a SFN is since
working on PCs from
Unless you depend on something that happens after StartService, then I would
do it next to that action. Make sure it is a deferred action without
impersonation.
-Original Message-
From: Dave Kolb [mailto:d...@dotnetcodeslingers.com]
Sent: Tuesday, October 13, 2009 8:47 AM
To: 'General
Brant, Know anyway for wix to check that I am installing on NTFS and not a
FAT system? I have no desire whatsoever of perpetuating anything in regards
to FAT...Thanks, Dave
-Original Message-
From: Brant Gurganus [mailto:br...@gurganus.name]
Sent: Tuesday, October 13, 2009 3:00 PM
To:
Sorry, I misunderstood, and the reference to NTFS didn't prompt me to what
you were saying. String table entries can permit a longer displayed shortcut
name where you are not limited by the filesystem limitations (abet much more
permissive than 8.3 was). That also allows you to show otherwise
Long file names can be turned off on NTFS so you have to worry about
it there as well. See
http://blogs.msdn.com/astebner/archive/2005/01/27/362049.aspx
Brant Gurganus
http://gurganus.name/brant
On Tue, Oct 13, 2009 at 4:09 PM, Dave Kolb d...@dotnetcodeslingers.com wrote:
Brant, Know anyway
Blair,
Yes I was speaking of the installer's command line parameter. I have been
reading over some blogs and examples and I want to make sure I have this
correct.
I can use the session to access the command line parameters and then assign
those to Wix in this kind of structure
File
Hi,
when trying to adding a shortcut util:InternetShortcut
Id=OutpostCentral Name=Outpost Central Website
Target=http://www.outpostcentral.com//
when it installs it doesn't seem to have an icon. The other shortcuts
I have do seem to have an appropriate icon though.
any ideas why?its being
I know how to install a file as a hidden file using the Hidden attribute as
shown below. What I would like to know id how do I create a directory that is
itself a hidden directory?
Thanks
-SteveL
HOWTO install a file as a hidden file:
File Id=Foo.txt ShortName=Foo.txt Name=Foo.txt KeyPath=yes
I apologize if this question is answered in an FAQ or email somewhere. I
didn't turn up much when I was searching this mailing list.
I'm running into a problem with TARGETDIR or SourceDir. I always want my
install to go onto C: (or the SystemDrive environment variable), but my
installs are
Interesting. I still think I will not specify short names so as to let them
auto generate and see if I ever run into problems. Thanks, Dave
-Original Message-
From: Brant Gurganus [mailto:br...@gurganus.name]
Sent: Tuesday, October 13, 2009 4:23 PM
To: General discussion for Windows
Is this with IE7 and you get the generic icon with the folded corner in
the upper right? If so, this is actually an IE7 bug. The icon in the
resource file was referred to with an incorrect GUID in the registry.
I'll see if I can dig up a link that describes it.
Problem, if it is the same, didn't
Some of these people are talking about the issue with IE7 and URL
shortcuts and some are talking about another issue (with IE7 and
favicons). Both of them are annoying issues.
http://social.msdn.microsoft.com/forums/en-US/iewebdevelopment/thread/10
ccd717-bd2c-487d-ab42-4a0a8dbf0293/
error LGHT0204: ICE03: Invalid format string; Table: XmlFile, Column:
ElementPath, Key(s): RollCall.exe.config.project
util:XmlFile Id=RollCall.exe.config.project Action=setValue
ElementPath=/configuration/applicationSettings/RollCall.Properties.Settings
The products are registered for Add/Remove Programs (whatever the platform
calls it) via the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
registry key by Windows Installer.
The HKLM\Software\[Company]\[Product] key is a best-practices location for
per-machine configuration, and the
In your wixlib, use only DirectoryRef elements as needed. Under your Product
and Module elements for each of the two packages supply the appropriate
directory tree.
-Original Message-
From: Dave Mateer [mailto:dave_mat...@ntm.org]
Sent: Tuesday, October 13, 2009 7:30 AM
To:
Not sure how you would run your ugly hacking code, nor how you would locate
the window with your controls. It isn't documented and your custom action
would run in a different process.
The external UI can run actions within the package before it starts the
installation sequence (such as AppSearch
The XmlFile element implements two custom actions for you: an immediate one
that the element itself schedules that reads a custom table that the element
adds rows to, and a deferred one that is scheduled by the immediate one,
receiving the data retrieved by that immediate one and acting on it.
No such support natively exists in Windows Installer. You would need a
custom action.
-Original Message-
From: Steve Lessard [mailto:sless...@microsoft.com]
Sent: Tuesday, October 13, 2009 1:44 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Hidden files
ROOTDRIVE in non-administrative installations is always set (if you don't
set it yourself) to the local drive with the largest amount of free space.
See http://msdn.microsoft.com/library/aa371372.aspx
Add this to your setup authoring:
CustomAction Id='SetRootDrive' Property Id='ROOTDRIVE'
/configuration/applicationSettings/RollCall.Properties.Settings/setting[\[]
[...@key='project'[\]]/@value
Would become:
/configuration/applicationSettings/RollCall.Properties.Settings/settin...@k
ey='project']/@value
Except that the repeated [ char is confusing the formatted syntax parser
since
I found the cause of your hang. Your vs2008 DLL creates a ProgId
CoKavBaseAbout.1 that is NOT version-independent that contains a CurVer
subkey pointing back at itself. Your vs6.0 DLL does NOT contain that extra
CurVer key.
Version independent ProgIds are supposed to point to their current
Is ROOTDRIVE the right thing to modify? Should I modify SourceDir or
TARGETDIR instead? I have to do a custom action for this? I can't get
away with setting a particular property and having it use that? I'm not
complaining. I'll do this. I'm learning that I know less than what
little I thought I
Ultimately what kind of paths do you want for your product's installation?
What do you wish as far as customizability of your customers regarding those
paths?
If you simply want to ensure that the default installation drive is
%SystemDrive% AND you are not using one of the predefined paths (such
Is there somewhere written up an overview of the flow of the installer in
general and how sequencing actions work? I would like to better understand
how to sequence actions and am confused about CustomActions
Execute=Immediate|Deferred|etc. vs. Custom Action Before= and After= and
how they work
Hi Blair,
Thanks for your response. I added RemoveFeatures to CD. After this If I done
the major upgrade, There are 2 entries in Add/Remove Programs. What might be
the reason?
Please suggest how can I solve it.
Thank you once again.
Blair-2 wrote:
It should, depending on how your product
from ESET NOD32 Antivirus, version of virus signature
database 4504 (20091013) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
--
Come build with us! The BlackBerry(R) Developer Conference
is the
scope
of the script.
Thanks, Dave
__ Information from ESET NOD32 Antivirus, version of virus
signature
database 4504 (20091013) __
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
59 matches
Mail list logo