It also requires that the service is setup to allow non-elevated privileges
to stop it.
Event Viewer\Windows Logs\Application
Source: RestartManager
-Original Message-
From: Joel Budreau
Sent: Tuesday, June 25, 2013 6:22 PM
To: afor...@cmu.edu ; General discussion for Windows Instal
An empty PatchFamily is "the" way to have that one PatchFamily cover the
entire product. Your error message is symptomatic of something else.
Do you have a stack trace of that error? Do you have anti-virus software
running on your 'c:\tmp\' folder?
-Original Message-
From: John Daintree [
-b tells the binder additional locations where to locate files that are
referenced in the wixobj files (the source locations of File, Binary, and
other related elements), not the wixobj files themselves.
-Original Message-
From: Marc Mirucki (Counterpunch Software LLC)
[mailto:v-mam...@mic
different bitnesses in the same transaction,
they must be in 64-bit-then-32-bit order.
Blair
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: Friday, April 01, 2011 1:11 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] DTF Transacti
Is in the same Component as
the registry entries you provided below?
Blair
-Original Message-
From: Shashikant Saini [mailto:shashikant.sa...@imail.org]
Sent: Monday, April 18, 2011 3:31 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] CodeBase value coming empty on ActiveX
re some discussions on wix-users before that feature request was
filed discussing issues that were reportedly fixed in the newer DifxApp
builds, so it may be worth your while to upgrade to 3.5.
Blair
-Original Message-
From: Rob Hamflett [mailto:r...@snsys.com]
Sent: Thursday, April 21, 2011 5:3
Please file a feature request so it doesn't get lost in the email list.
Blair
-Original Message-
From: Alex Ivanoff [mailto:alex.ivan...@shavlik.com]
Sent: Thursday, April 21, 2011 7:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Integri
Depends on when your custom action is scheduled. Can you describe in more
detail what you are trying to achieve?
Blair
-Original Message-
From: Rune Moberg [mailto:jjfl...@gmail.com]
Sent: Saturday, April 23, 2011 1:18 PM
To: General discussion for Windows Installer XML toolset.
Subject
se heat in your
build, use -ag not -gg. If you can reuse the previous component guids you
have a better chance of success (you can still have problems if any files or
other keypaths were removed).
Blair
-Original Message-
From: Preethi S. [mailto:preet...@amiindia.co.in]
Sent: Thurs
attribute?
Blair
-Original Message-
From: David Rickard (USA) [mailto:davri...@microsoft.com]
Sent: Monday, April 18, 2011 4:18 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Patch install failing on Server 2003 - Error 2920
Ran ICE on the MSI+Patch
I'm curious: what happens if you include but disable the cancel button?
-Original Message-
From: Tobias S [mailto:tobias.s1...@gmail.com]
Sent: Wednesday, April 27, 2011 5:13 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] old unanswered question rega
Create a Feature Request on SF?
Blair
-Original Message-
From: Christopher Painter [mailto:chr...@deploymentengineering.com]
Sent: Thursday, May 05, 2011 6:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Creatin User Group and add current user
Are you using the same UpgradeCode?
Blair
-Original Message-
From: James Robertson [mailto:ja...@osodata.com]
Sent: Friday, May 06, 2011 4:58 AM
To: WiX
Subject: [WiX-users] 32-Bit < > 64-Bit
Hi,
I have an existing installer for a 32-bit application that has been working
fine f
Look at ComponentSearch.
Blair
-Original Message-
From: Aaron DeMarre [mailto:adema...@gmail.com]
Sent: Friday, May 06, 2011 1:38 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Property Behavior in Repair vs. Upgrade
I am wondering if there is a way to get my major upgrade
the WIXPDB.
Alternately you can write a BinderFileManager (which you place into a
WixExtension you pass to light) where you override the one of the
ResolveFile() methods (use the easiest one that works for your setup).
Blair
-Original Message-
From: Elfe Xu [mailto:elf...@microsoft.com]
Sent: Mo
h.
A verbose log should tell you why you are getting features set to install
when you apply the patch.
Blair
-Original Message-
From: Christoph Vollmer [mailto:christoph.voll...@emendo.co.nz]
Sent: Monday, May 09, 2011 4:21 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-
m that way.
In fact, your CoPr value would have to be constrained to ensure that you
don't create reserved or otherwise defined elsewhere GUID types.
Blair
-Original Message-
From: Aaron Klor [mailto:aaron.k...@gmail.com]
Sent: Monday, May 09, 2011 7:06 AM
To: General discuss
And the set of before the CoPr are not random values either, and you
will need to ensure that they don't conflict with the GUID specifications
either.
Blair
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Monday, May 09, 2011 10:11 PM
To: 'General disc
ersely, if you change the interface or otherwise require a new binding,
you change both versions.
-Blair
-Original Message-
From: Christoph Vollmer [mailto:christoph.voll...@emendo.co.nz]
Sent: Monday, May 16, 2011 10:48 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users]
ou already agreed to.
Know that this is solely my opinion and does not bind the WiX toolset,
Microsoft Corporation, or any other party in any way. Talk to your attorney
before you rely on it.
-Blair
-Original Message-
From: Timo Viitaniemi [mailto:timo.viitani...@crosscontrol.com]
Sent: Wed
e.net/manual-wix3/heat.htm
for details on heat.
-Blair
-Original Message-
From: Andreas [mailto:andreassand...@gmx.net]
Sent: Tuesday, May 24, 2011 10:22 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Votive: Reference Properties
Hello,
I hope I am here at the right place for
r, upgrade,
everything). Make sure your custom action is an immediate custom action so
that it can set the properties. Know that immediate custom actions are not
normally elevated, so hopefully you can read Excel's registry key without
requiring elevation.
-Blair
-Original Message--
WiX's element can copy arbitrary files to arbitrary directories.
You can reference the installation MSI via the OriginalDatabase Windows
Installer property.
-Blair
-Original Message-
From: Michael Stoll [mailto:unwicht...@mistoll.de]
Sent: Thursday, May 26, 2011 5:23 AM
To: wix-
e MSP file itself?
-Blair
-Original Message-
From: Nangai [mailto:thangananga...@iinterchange.com]
Sent: Thursday, May 26, 2011 5:04 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Unable to execute SQL script from patch msp
Hi,
I am using Wix 3.5.2519.0 to create patch. I am
What does a verbose log say? If you are not certain as to the value of your
IUSR_USERNAME property, it will be hard to verify that what account was
given write access to your file.
-Blair
-Original Message-
From: gapearce [mailto:mr_gapea...@yahoo.com]
Sent: Wednesday, May 25, 2011 12
There is not current code in WiX to set arbitrary permissions on
certificates installed via WiX.
If someone can dig up the APIs used to set permissions on certificates, that
could be added
-Blair
-Original Message-
From: Will Gross [mailto:mastermind...@gmail.com]
Sent: Wednesday, May
Heat "out-of-the-box" does not currently gather project's dependencies. That
is currently a manual task. There was a recent thread on this email list
discussing the difficulties with automatically gathering
dependencies/references.
-Blair
-Original Message
sions of a
certificate installed by wix.
Just added it.
(http://wixcontrib.codeplex.com/SourceControl/network/Forks/mistoll/WixIssEx
tension)
Michael
Am 28.05.2011 02:38, schrieb Blair Murri:
> It's not dead, it just hasn't been updated in a very long time.
>
> Go ahead and add
uses all four numbers (none
are ignored) of the patch sequence number, to achieve upgrading and prevent
downgrading.
Blair
-Original Message-
From: Justin Hull [mailto:justin.h...@assetpoint.com]
Sent: Tuesday, November 15, 2011 12:22 PM
To: General discussion for Windows Installer XML
ned preserving/restoring those
properties in your previous topic.
Blair
-Original Message-
From: justin hull [mailto:justin.h...@assetpoint.com]
Sent: Tuesday, November 15, 2011 2:48 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Getting error on writing INI section using addline
element?
-Original Message-
From: AxiomaticImpact [mailto:ke...@legendary-immersion.com]
Sent: Tuesday, November 15, 2011 2:11 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Enable/disable "Next" button
--
View this message in context:
http://windows-installer-xml-wix-too
The only clean ways I am coming up with involve various schemes to force the
component containing that RemoveFolderEx element to remain "installed" (and
presumably orphaned) when the product containing it is removed. Does anyone
else want to weigh in with ideas on that theme?
Blair
---
>From the point of view of the installation sequence, user input from custom
forms and command line are the same thing.
Blair
--
All the data continuously generated in your IT infrastructure
contains a definit
Add a transform to heat's commandline that adds the Verb.
-Original Message-
From: Peter Bulyaki [mailto:peter.buly...@gmail.com]
Sent: Monday, November 21, 2011 8:27 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Problem with file association and harves
Daniel,
How many WXS files cause VS2010/MSBuild to croak? I haven't seen that.
Blair
--
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application perfor
$(var.MyEnableCondition)
NOT ($(var.MyEnableCondition))
7) Stable release
Right now 3.5 was RTM about 9 months ago, and 3.6 was declared Beta almost a
month ago.
Your welcome,
Blair
-Original Message-
From: Calin Iaru [mailto:ca...@dolphinics.no]
Sent: Thursday, November 17, 2011 3
ops the
build before the other error could ever surface.
Are you harvesting your C# projects from your WiX project? How are you
"handcrafting" your references? What settings/properties have you set wrt
your harvesting?
That is where I would start my investigation.
Blair
-Origin
en by properties being set, and others don't. I suspect you ARE
creating those directories, just not where you think you are. Please review
your entire directory tree.
Blair
--
All the data continuously generated
omponents containing CreateFolder elements.
Blair
-Original Message-
From: mat_macwilliam [mailto:marcus.macwill...@1spatial.com]
Sent: Wednesday, November 30, 2011 2:18 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] CreateFolder is not creating required directory
structure
y ship the same EXE binary in all builds. That way,
you can update the code of the service while not having to reinstall the
service on each upgrade.
-Blair
-Original Message-
From: Michael Janulaitis [mailto:wix-u...@cornerbowl.com]
Sent: Wednesday, November 23, 2011 11:16 PM
To: General
To be a major upgrade the RemoveExistingProducts action must be
scheduled/run.
-Original Message-
From: Robert Lee [mailto:genrobert...@gmail.com]
Sent: Wednesday, November 30, 2011 3:12 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Is major update supposed to duplicate the
ld I
need to put the condition checks on each feature to be installed?
-Original Message-
From: Blair [mailto:os...@live.com]
Sent: Wednesday, December 09, 2009 12:38 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Conditions in merge
, December 09, 2009 12:56 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] How to specify files in Installer package
Hi Blair!
Those directories contain many files and I don't want to specify them by
hand.
And if I want to ignore .svn directories, I'm fully out of luck.
Addit
ng to that
location.
Blair-2 wrote:
>
> Are your patches MSP files performing either small updates or minor
> upgrades? If so, the patch application won't let you patch anywhere other
> than the currently installed location since the keypath of the components
> can't
The intent is:
- A major update is an update that "replaces" all previous versions of a
product. It never requires (usually) the previous version to be installed.
- A minor update is an identical copy of an original with some "minor"
changes. You can't really remove anything in the "replacement p
You will increase your success rate by doing these things:
- Get rid of your self-registration and use the built-in Windows platform
support for services (the Service* elements in WiX).
* the above will require that you perform all your registration using
Registry entries, etc. in the MSI itse
What does the log say about the component statuses?
-Original Message-
From: XorPtr [mailto:reaper4...@gmail.com]
Sent: Thursday, December 10, 2009 6:27 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Patching problems with alternate directories
Hey Blair-2, I'
er 10, 2009 12:00 PM
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Patching problems with alternate directories
>
>
> All of the components are listed as:
>
> Installed: Local; Request: Local; Action: Local.
>
>
> Blair-2 wrote:
>&g
If the file didn't exist in the baseline image there really shouldn't be a
difference for that file by merely adding the delta switch.
Is this something where you can share the wixmst file with me?
-Original Message-
From: nearnick [mailto:n...@nearglobal.com]
Sent: Thursday, December 1
Copy WixUI_InstallDir.wxs from the sources to your project, remove the
offending property, and refer to your copy instead of the one in the
extension.
Later, address the maintenance mode dialog sequence to ensure it works for
you.
-Original Message-
From: Robert Hermann [mailto:rob.herm..
rsionNT > 400
NOT SKIPINSTALLSQLDATA AND VersionNT
> 400
VersionNT > 400
VersionNT
NOT REMOVE~="ALL" AND VersionNT >
400
"VersionNT>=600"
VersionNT
-Blair
-Original Message-
From: Tony [mailto:yellowjacketl...@gm
At the bottom of each page, the author's name is a hyperlink that opens a
partially populated email message to compose (assuming your email client and
your computer's browser are both setup for that). Here is that hyperlink:
mailto:d...@tramontana.co.hu?subject=wixtutorial
-Original Message---
I agree that this is a reasonably good method to deal with the per-user
configuration that inevitably ends up falling on the setup developers to
supply. The one thing to keep in mind is how to trigger that "last part of
install" for the non-installing users (assuming your installation is
per-ma
If the ProductCode you are attempting to install is already installed, it is
no longer a major upgrade and is a maintenance mode transaction (see small
update & minor upgrade, as well as repair and removal). Your ProductCode
must not be installed in order to perform an installation transaction (bot
ck on the account dialog
asking them to verify the information they provided.
This isn't as much of an issue for the group membership function as we
can only add the user to existing groups. So, a simple type-o won't
fail the install.
On Mon, Dec 14, 2009 at 4:11 PM, Blair wrote:
>
Also, Daniel, to attempt to help you answer your question as to the difference
in behavior caused by the addition of the InstallExecute and the placement of
MsiProvideAssembly, it helps to understand the following about Windows
Installer:
Everything you see in any sequence table you should cons
After CostFinalize [#fileid] is the full path to your File with Id of
"fileid" during installation without any "%" characters in it. Also,
[directoryname] is the "\"-appended full path to the Directory with the Id
of "directoryname". So you can use both of these patterns in creating your
registry e
The problem isn't so much with MessageBox specifically as it is with UI in
general: Windows Installer doesn't support custom UI all that well. The
"built-in" support for what you are trying to do is called either "embedded
UI" or "external UI", not showing dialogs from your immediate custom
actions
Why does your installer require admin to run? Are you bootstrapping things
in addition to your MSI?
-Original Message-
From: little.forest [mailto:little.for...@ymail.com]
Sent: Wednesday, December 16, 2009 11:08 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to launch ap
Sometimes Windows Installer will send you install messages what, when AND'd
with INSTALLMESSAGE_TYPEMASK, are not something you recognize. If you return
an error (-1) you just failed your transaction and if you return any other
non-zero value you just bypassed whatever it was attempting (which is b
You need two components, one marked 32-bit and the other 64-bit. Each will
write to the appropriate areas of the system. Yes, you will have some
duplicate information shared in both components, but each will refer to the
appropriate binary and each should be under the appropriate directory.
-O
Currently you copy the dialog's sources into your code and change the values
you want. Refer to the help, blogs, this list, and tutorials to see how.
-Original Message-
From: Petr Pokorný [mailto:ppoko...@intermap.com]
Sent: Friday, December 18, 2009 3:06 AM
To: wix-users@lists.sourceforg
What you don't mention are the following:
Which of the 21 MSIs are written in WiX (as opposed to InstallShield) and
how many (of each) are written in older versions of each of those two
toolsets.
Will you be supplying your own UI binary (a bootstrapper) or will you be
attempting to combine the va
You would need to calculate a guid using your version number to use as your
ProductCode (such that the same version number always generates the same
guid and different version numbers generate different guids).
Either a hash-based guid generator or a V1-style guid, I would think.
-Original Me
Back to your original authoring:
CostFinalize is run twice in any given installation with UI: during
InstallUISequence and during InstallExecuteSequence. Is MYPROPERTY marked as
secure? If it isn't, it will be 0 (the default) during
InstallExecuteSequence (not whatever you set it as during
Install
The on the components is evaluated during CostFinalize, not
CreateShortcuts. You don't get the shortcuts because the components
installing the shortcuts are not being installed due to the false condition
on them.
I would recommend moving your CheckApplicationLicence custom action sequence
to befo
You need to use MsiProcessMessage with the INSTALLMESSAGE_USER type. See
http://msdn.microsoft.com/library/aa369205.aspx for details.
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Tuesday, December 22, 2009 5:13 AM
To: wix-users@lists.sourceforge.net
Subject: [Wi
The Upgrade table/RemoveExistingProducts action cannot cross scopes. You
will have to use a bootstrapper to remove the old per-user installation.
-Original Message-
From: Evan Beeton [mailto:ebee...@informasoftware.com]
Sent: Tuesday, December 22, 2009 11:23 AM
To: General discussion for
.MSI database, thus it isn't expected that they would require
admin privs or any other reason that the action would be anything other than
immediate.
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Tuesday, December 22, 2009 9:54 PM
To: 'Blair'; &#x
You can try setting the packa...@readonly attribute. As far as I know Orca
respects the read-only selection but I have never tried it myself. However,
the APIs don't seem to prohibit editing (and committing) "read-only" MSI
files.
If your MSI file is authenticode-signed than any editing at all wil
I would recommend using the DTF "wrapper" for C# (or any other .net) custom
actions. If your C# code is AnyCPU you won't need to worry about bitness for
the CA code itself using DTF.
Otherwise, 32-bit CAs work in all 64-bit systems that have WoW64 present
(see
http://blogs.msdn.com/heaths/archive/
I don't know, but look at CustomizeDlg.wxs in the sources for ideas since
that is the .wxs that incorporates BrowseDlg and it seems to employ the same
features you are trying to enable in your ChangeFolderDlg.
-Original Message-
From: Sagar [mailto:sagarkavitak...@gmail.com]
Sent: Tue
How about this?
NOT ($(var.InputValidated))
$(var.InputValidated)
Yes, I realize that this maintains the double-evaluation, but it is more
maintainable (since you type it only once) and the time to evaluate
ad
of create)
_
Van: nagaram.c [mailto:nagara...@symphony.cc]
Verzonden: do 24-12-2009 6:46
Aan: 'General discussion for Windows Installer XML toolset.'; 'Blair'
Onderwerp: Re: [WiX-users] writing to console from smoke.exe using
customaction
I found a solution, the custom a
As I understand it, the SourceDir property must be the root of the source
tree (the directory tree that the files and folders you are installing), and
it is set to be the directory location of the MSI file itself.
Can you move setup.msi to the Conent folder?
-Original Message-
From: V0id
Windows Installer evaluates component conditions during CostFinalize, so
your custom action that sets those session values must be scheduled before
then. I would recommend scheduling those types of actions to run before
CostInitialize, just to have a "smoother" flow.
-Original Message-
Fro
You could try an "administrative install". You could also try heat.exe's
extraction option.
The APIs involve extracting the cabs and then using the cabinet APIs to
extract the files, for the cases where the files are compressed & embedded.
For external cabs, just the cabinet APIs. For non-compres
quot;C"' and are also listed in the .def
file to prevent any form of compiler/linker decoration.
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Sunday, January 03, 2010 10:08 PM
To: 'Blair'; 'General discussion for Windows Installer XML to
The only thing you can do is compare the current value of the property
against the known default value. If the command-line value is the same as
the default value you wouldn't ever be able to know.
The only way to know for sure if a property was set from the command-line is
to not have the propert
eturn (int) error;
}
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Monday, January 04, 2010 5:20 AM
To: 'Blair'; 'General discussion for Windows Installer XML toolset.';
'Schrieken, Rene'
Subject: RE: [WiX-users] writing to console from sm
Easiest way is via .WXL files. Since each can contain just one culture you
simply use that file to set the codepage (and don't set the codepage in the
database code itself). The biggest limitation with this idea is you can't
directly set the summary codepage this way, but you can use loc variables
Most patches should not have any references under PatchFamily (nor more than
one PatchFamily). That will cause ALL changes between the target and
upgraded images to be included in the patch.
Some (generally very large and complicated) setups require scoping the
changes into groups/series/buckets w
installer dialog using WIX 3.0?
Blair, if we don't have ANY references under PatchFamily, how can we tell
WIX which change should be included in the patch? Without listing every
changed component/property/etc. in the patch WXS file, none of the changes
are making to the final MSP.
FYI, I am able to
Look at InstanceTransforms element?
-Original Message-
From: angela jones [mailto:suggestionang...@gmail.com]
Sent: Monday, January 04, 2010 3:37 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] multiple instances wix source code
Hello,
I have built and msi for install
s] How to patch an installer dialog using WIX 3.0?
Thanks for the explaining that Blair. I already have everything in place for
the PatchFamily and PatchFamilyRef. So, that part is good and I am able to
generate the patch without any issues.
The only thing that I am not sure is if I can use the U
[mailto:nagara...@symphony.cc]
Sent: Monday, January 04, 2010 10:39 PM
To: 'Blair'; 'General discussion for Windows Installer XML toolset.';
'Schrieken, Rene'
Subject: RE: [WiX-users] writing to console from smoke.exe using
customaction
It looks like MsiProcessMessage work
summary codepage myself (since I have usually had to
> deal with "unicode-only" languages).
You lost me here. I understood the first part...
On Mon, Jan 4, 2010 at 5:06 PM, Blair wrote:
> Easiest way is via .WXL files. Since each can contain just one culture you
> simply use
The sourceforge group email system often strips attachments. Please consider
posting the wxs file to a server somewhere and include a URL in the email to
retrieve it.
Thanks.
-Original Message-
From: Helgi Hrafn Gunnarsson [mailto:he...@binary.is]
Sent: Tuesday, January 05, 2010 7:29 AM
During your "change" transaction set the REINSTALL property to include the
feature(s) that include the components you would like to change.
-Original Message-
From: Kevin Garman [mailto:gar...@scadaware.com]
Sent: Tuesday, January 05, 2010 6:19 AM
To: General discussion for Windows Instal
Add
To your authoring
-Original Message-
From: Balu Swaminathan [mailto:bswa...@hotmail.com]
Sent: Tuesday, January 05, 2010 10:55 AM
To: wix user list
Subject: [WiX-users] Passwords, hidden and the log file
Hello All:
I have:
and the value passed on PASSWORD is writt
te OS platforms (like Chinese and
Japanese), how is this possible? Or is that what you mean by having a
"UTF-8 database"? I know UTF-8 encoding supports multi-byte character
sets. So, maybe that is how these msi are working?
On Tue, Jan 5, 2010 at 1:40 PM, Blair wrote:
> If you no
What you don't say is whether what you ship are the merge modules themselves
or if you simply use them as internal "global" libraries for the MSIs you
build. You also don't say whether you are porting all at once or in stages.
-Original Message-
From: Bill Packard [mailto:bill.pack...@kepw
I know that the WixVsExtension defines properties like VS90_SCHEMAS_DIR that
would be the directory you would need to place the .xsd file into. Use the
appropriate property for the version of Visual Studio you are targeting.
Beyond that, either MSDN or the forums on MSDN would have much more
infor
Is it at all possible that the new ICE900 test you wrote uses the C++
runtime DLL?
In your C++ build settings you need to make sure you link to the static
runtime library AND that you build Release (not Debug) for the version you
run away from the developer's box.
-Original Message-
From:
ation dialog), change
the Runtime Library setting to "Multi-threaded (/MT)", then hit Apply and
OK.
-Original Message-
From: nagaram.c [mailto:nagara...@symphony.cc]
Sent: Wednesday, January 06, 2010 5:17 AM
To: 'Blair'; 'General discussion for Windows Installer
If you use the MSI, it only allows one installation of WiX at a time
(installing 3.5 will replace 3.0).
Other than that, I have not yet used 3.5 with VS2008, so I wouldn't know of
any issues with opening the files, but you can always disable building the
3.0 WiX project before you install 3.5 and
Preagent.exe is a file you are installing, using for configuration, or both?
You need to call it with those parameters as the installing user or
elevated? It needs to be visible to the user when it runs or not? It should
have those parameters every time it runs or just once? Can you do the same
thi
ortly
thereafter you convert the MSI projects to WiX, however.
-Original Message-
From: Bill Packard [mailto:bill.pack...@kepware.com]
Sent: Wednesday, January 06, 2010 6:44 AM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Shortcut path for Merge modules
Blair,
The merge mo
Your keypath is 'DT.MyDir' (as you have authored it).
-Original Message-
From: Jeff Perrigo [mailto:jeff.perr...@microsoft.com]
Sent: Wednesday, January 06, 2010 5:18 PM
To: General discussion for Windows Installer XML toolset.
Cc: Bob Arnson
Subject: Re: [WiX-users] Performance Counters
eters
without running it?"
Sorry, I didn't understand this quastion..
Thanks for your time,
Shlomi
On Wed, Jan 6, 2010 at 6:26 PM, Blair wrote:
> Preagent.exe is a file you are installing, using for configuration, or
> both?
> You need to call it with those parameters as the insta
1 - 100 of 2073 matches
Mail list logo
