Consider using ProgramFiles6432Folder to initialize the burn variable.
http://wixtoolset.org/documentation/manual/v3/bundle/bundle_built_in_variables.html
When the chain needs to install both 32 bit apps and 64 bit drivers on a 64
bit system then I define two burn variables InstallFolder and
Insta
Soren started the thread "Displaying custom error messages if deferred CA
fails" several days ago, and I have been trying to resolve a similar
problem.
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Displaying-custom-error-messages-if-deferred-CA-fails-td7594643.html
My CA is C++ an
I have been following this thread and trying to figure out a similar issue
using WcaErrorMessage in my CA and trying to catch the error event and
display a message in my Burn mba. I did not know how similar this was to
your (Soren's) efforts, so I started another thread here:
http://windows-insta
>>WiX Extended Bootstrapper Application by Neil Sleightholm
https://wixextba.codeplex.com/
This site is not really related to creating a mba. It is about how to
extend the WixStdBA in wix 3.7 by creating a BAFunctions.dll. Most of this
functionality is integrated into Wix 3.8 (and later), but
I use an mba now, so not using WixStdBA for a while. You can use a formated
Burn variable to set LaunchTarget, and you can modify a Burn variable based
on user dialog selections using the BAFunctions.DLL.
https://wixextba.codeplex.com/ has details and samples related to using the
code hosted thei
Look at a verbose MSBuild log. The Clean target is probably fired by VS.
There are a number of reasons why this might be the case. Changes would
depend on your business requirements. You might add a MSBuild task which
copies the files to a common area on a successful build.
--
View this mess
I would enable verbose logging on the test system and then review the log
after the on-demand install happens.
http://support.microsoft.com/kb/223300
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Wix-Installer-runs-after-upgrade-if-running-instal
I have a MSI project which has been building and deploying successfully for
some time. However just before a left a week ago for vacation something
changed and I now get the LGHT0136 error relate to the Upgrade Table. I'm
not sure what changed and I tried to revers different changes and track thi
I used to use a wixlib project but when I added multiplatform projects and
tried to use MSBuild directly for my build process I had problems with a x64
project failing due to a dependency on the wixlib project (which had already
been built) but would not build with platform set to x64.
So for wx
Hi Bob;
Thanks a lot for the insight. I stared at that and did not pick up on the
line feed which had broke the Product/@Version entry.
Thanks;
Phill
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/LGHT0136-error-importing-table-Upgrade-tp759510
I do not have direct experience with this issue, but I suspect the thing to
do is to leave the new package name as is, but rather author multiple
upgrade codes to also remove the old product.
http://www.joyofsetup.com/2008/09/07/hint-be-generous-with-upgrade-codes/
--
View this message in conte
>>>DIFXAPP: INFO: No matching devices found in INF
"C:\Windows\System32\DriverStore\FileRepository\pxlgevndis6.inf_amd64_ne
utral_fe3715a4af78ac12\PxLGevNdis6.inf" on the Machine.
I would configure the target system to generate a verbose setupapi log, and
study both (msi and setupapi.dev.log)
Take a look at using Root="HKMU"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Vary-registry-hive-at-runtime-based-on-InstallScope-tp7595160p7595169.html
Sent from the wix-users mailing list archive at Nabble.com.
---
True, zero is returned on success. A non-zero return may indicate a failure,
or it may indicate 'no action taken' (0x8007015e), a reboot is needed (3010)
or some other condition.
http://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx
--
View this message in context:
http://windows-inst
A Bundle is not processed by msiexec.exe and does not have a "Property" in
the MSI sense of the term. A Burn Bundle may have Burn "variables", which
are a slightly different concept than a "Property".
You cannot "set" the variable in the Bundle (wxs authoring), but you can
make it bal:Overridable
The symptoms that you have shared, (installs on a clean system, but when the
"old" driver is present, the "new" driver is added to the driver store, but
the class installer is not invoked by the PNP manager) are commonly due to
the fact that the "new" driver has a lower driver rank than the "old"
d
Did you see this thread?
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-Burn-patch-for-bundle-td7291580.html
Some time ago I did an experiment along this line. I think I used 'add-in'
or 'update' but not 'patch'. And I added code to my mba. For me the
updated bundle was remove
You have Return="ignore" which means "the custom action will run
synchronously and the return code will not be checked".
If you want the action to run asynchronously then use Return="asyncNoWait".
(I have not done this so I don't know if there are other issues,
particularly related to the fact th
I may be speaking out of turn, but from what I have read, the XML is output
if the change does not require changing any file objects. If the patch
deploys files then they are also added to a cab. (I hope this is correct
and I apologize if I have mislead anyone.)
--
View this message in context
I should have tested more before I did the above post. The above change does
not work, so I will go back and study how to do RemotePayload some more.
Thanks.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Third-party-payload-download-from-my-ser
The WIX source "src\Setup" is the setup for the wix toolset and is a great
example of packaging different 'features' in different MSIs and then using a
Bundle to chain the MSIs, dependent EXEs, etc. Combined with the download
functionality and using either a Burn mba or the WixStdBA (with a
bafunc
I have not done this with Net 1.1, but I did something similar with Net 3.51.
In the Bundle use util:RegistrySearch for the registry value mentioned in
the following link, with Result=exists". The use the result in the
DetectCondition so that when true the package should not be launched.
http://
Did you consider using util:XmlConfig and UILevel. (I have not done this,
but looking at the documentation it seems likely to work.)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-differentiate-silent-installer-or-interactive-installer-in-
Where is the ComponentGroup Id="SimpleWebAppGroup" defined? To use a
There also needs to be a:
with one or more Component elements defined.
--
View this message in context:
http://windows-
A string should be enclosed in quotes, but in a XML statement use the html
entity " or use CDATA.
http://wix.tramontana.co.hu/tutorial/com-expression-syntax-miscellanea/expression-syntax
http://www.ascii.cl/htmlcodes.htm
DetectCondition=" GOTO_ASSISTEXISTS =
&qout;$(var.GoToAssistExpertName)
Check out this link from the on-line help (or chm), particularly the part
about customizing text.
http://wixtoolset.org/documentation/manual/v3/wixui/wixui_customizations.html
I have not used the WixUI library, but in searching the wix source code with
notepad++, it looks like the strings are defi
See this post:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Running-Burn-driven-installer-in-quiet-mode-command-line-parameters-td5913001.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Silent-Install-of-Bootstrapper-tp7595350
One approach, which may not be sanctioned and may have risks, is to add code
to your mba, which imports the data from the
BootstrapperApplicationData.xml. There are examples of a class here which
you may need to modify for a specific purpose.
http://stackoverflow.com/questions/12846421/getting-di
The update behavior of msiexec and the UpdateCode property are specific to
MSI based technology. It would not know about other technologies like
InstallJammer.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Unable-to-uninstall-previously-installe
It sounds like the mba has a dependency file which should be added to the
bundle as a Payload element.
http://blogs.msdn.com/b/suzcook/archive/2003/05/29/debugging-assembly-loading-failures.aspx
Generally I would not test a setup on my development machine. No telling
what damage could be done.
I have been working on a similar problem today, with same error.
[14A0:14D8][2014-06-21T20:02:41]e000: Error 0x80070570: Failed to extract
all files from container, erf: 1:4:0
In my case the problem was induced by changes that I made to my mba, so the
problem was not intermittent. In my case I
Was the namespace added to the header of the wxs which uses the
BalExtension.dll elements?
xmlns:bal="http://schemas.microsoft.com/wix/BalExtension";
If this does not help you may need to post the relevant code from your wxs
file.
--
View this message in context:
http://windows-installer-xml-
I concur with John's post. I make sure all projects can be built using
scripts that call MSBuild and VS. I avoid using VS events (PostBuild) in
favour of BeforeBuild and AfterBuild nearly every project. There are other
helpful MSBuild targets which can be reviewed by enabling a verbose build
lo
I think this post explains the issues with using two different component IDs
to point at a single resource:
http://robmensching.com/blog/posts/2003/10/18/component-rules-101/
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Harvest-files-from-diff
If RadioButton1 is define as a numeric Engine variable, then use
'RadioButton1=1'. If RadioButton1 is defined as a string Engine variable
then test it against a string, i.e. 'RadioButton1="e;1"e;'
Either used html entities to put quotes around the string or use CDATA.
A Burn (Engine) var
I do not see any problem compiling this code against wix 3.8.1228 RTM
toolset.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperApplicationData-attribute-is-not-declared-tp7595444p7595605.html
Sent from the wix-users mailing list archive
I should add that I provided a full path to an msi rather than just a file
name in SourceFile="a32.msi"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperApplicationData-attribute-is-not-declared-tp7595444p7595606.html
Sent from the wix-u
If using VS, there should be a 'Reference' to that extension. Typically the
extension DLL is located in the wix toolset 'bin' folder (on my Win7 x64
that would be c:\program files (x86)\Wix Toolset v3.8\bin). Yours may vary
but the environment variable '%WIX%bin' should be set to the path to the
First I have not done this specific task of using Radio Buttons, but I read
information in the chm and on Niel's helpful web site
https://wixextba.codeplex.com/documentation. Note that the wixextba was
applicable to wix 3.7, and these features were ported into wix 3.8 with
samples in the wix 3.8 s
I have not tried to restart explorer, but in my msi I use the
util:RestartResource element to signal the Restart Manager to handle the
situation. The resulting behavior depends on how the application implements
support, which I would assume would be implemented in the OS applications.
http://blog
Not really the question asked, but are you aware of using heat to harvest
regasm entries?
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Re-To-regasm-or-to-not-regasm-td7580188.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/cal
The Windows Advanced Firewall expects, what the WixFirewallExtension calls
FirewallException/@Name, to be a unique string for each rule, otherwise
multiple MSI entries for the same firewall rule. I tend to use preprocessor
strings that equate to 'CompanyName AppName' so that they are grouped
toget
I would appreciate any advice on how to understand or resolve the following
problem.
I implemented a mba, and using the Wix (3.8) source (src\Setup) as a guide
to use the Update functionality. This functionality has been working in
several bundles (projects) which I have developed over the last s
IT is returning Content-Type: text/html
Actually for the above test I was not using my atom. I had copied the wix
toolset atom to my company site, just as an experiment to see if I could
validate someone elses atom coming from my server, and it also fails.
I can do it again with my atom.
I do n
I should clarify that when I point the validator.w3.org at my server, with a
known good atom, the validator fails. However Fiddler shows that the atom
was returned with Content-Type: text/html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/appsy
I have not done this with a C# dll CA, but I had a similar problem localizing
my mba C# dll. The C# dll gets loaded into a host. In the mba case the
host had already defined a resource dictionary using the default name. So
in my project (which is not in front of me now) I had to define resx file
I am still trying to understand this problem, so any pointers would be
appreciated.
I am using the wix38-debug zip package, pdbs and source, to step into burn
with windbg. The issue seems to show up in src\burn\engine\apply.cpp in the
AcquireContainerOrPayload at line 1117.
// If t
Thanks for the moral support. I found the core cause of the problem, in my
mba ResolveSource code. So the problem was not related to the Atom or the
web server configuration. Thanks to everyone who contributed to Wix and
the great appsyndication features.
--
View this message in context:
ht
Jacob, thank you for the posts! I had noticed the discussion about
self-updating bundles and the changes in 3.9. After some testing I
determined that this problem was not related to the atom feed. As soon as I
finish testing these changes, then I plan to migrate to 3.9. The root
problem was int
I just downloaded wix 3.9.702. (I currently have wix 3.8.1128 installed
using the wix setup.) While I downloaded the wix 3.9 setup, binary zip, and
debug zip, I did not use the wix 3.9 setup. Rather I extracted 3.9 binaries
zip to a folder on my system. I then browsed to wix.CHM in that tree an
No I had not done that. Thanks for the reminder!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix3-9-702-CHM-tp7595722p7595724.html
Sent from the wix-users mailing list archive at Nabble.com.
---
A console application is not a windows service, unless it implements code to
support the windows services API. The error indicates that the SCM sent an
event to the service and it did not respond (which makes sense if it was
just a console app and did not have any code to support the windows servi
I believe, and someone can correct me if wrong, that generally the
WixFirewallExtension supports the parameters which were available to the
Windows Firewall (XP era) which also works with the Windows Advanced
Firewall. But the extension does not provide a way to specify some of the
parameters of t
I upgraded from 3.8.1128 to 3.9.702 a few days ago, and I am observing a
change in behavior in the why my bundles are updated. (I am aware that
there are new features in 3.9 related to bundle updating, but was not
expecting this behavior change. At the same time I did not revert my build
system b
My mba which has been working in this regard for about a year, is based on
the Wix toolset Setup\WixBA\UpdateViewModel code which implements
DetectUpdateBegin and DetectComplete. Some time ago I added some
customization to these handlers to allow our build process to place builds
into a dev, test,
Jacob, thanks for all of the information.
My code is exactly the same as the snippet that you posted (except I added a
couple of calls to Engine.Log to see what the Url is that was passed to
Engine.Setup.) I thought that this code snippet related to parsing the atom
feed for multiple entries, how
A related behavior that I am observing is that when a Bundle is installed on
a system, it is being cached under both:
C\ProgramData\Package Cache\
\AppData\Local\Package Cache\
When a bundle is "completely" Uninstalled, the entries under C:\ProgramData
are removed, but the entries under ..\AppData
My concern is with "incremental upgrades instead of taking the largest leap
possible", which as I investigate seems to be related to the leftover bundle
in the user specific package cache.
When a user launches Bundle.exe 1.05 (and if 1.0.10 is available on the web
site, but if intermediate bundles
>>>you are seeing a behaviour where if A is installed and B was cached
previously, that when going to ARP and selecting modify that the update
check invokes B instead of downloading D?
If the user goes to ARP and D is already installed, then D is launched.
However if the user does not use ARP, b
After adding more logging statements that information is the same as above
but confirms that the DetectUpdateBegin and worker_DoWork detect the latest
version (on the web site if available).
But apparently prior to that event, when there are intermediate versions
cached locally (meaning a version
Yes. It is just defined so that someday in the future I could, if needed,
deploy a patch, addon, or upgrade. But at this point A - D are all
MajorUpdate of A (and I did not redefine the ReleatedBundl_GUID between
then. Should I change that with each MajorUpgrade? (I have been dong this
for mos
FYI - I have confirmed (using a different project which has not been changed
for some time) that when the bundle is built using wix 3.8.1128 it does not
have the behavior observed when the bundle is compiled using 3.9.702.
Specifically:
Bundle A (built using 3.8.1128)
Bundle B (built using 3.9.70
Yes UpdateReplace is indicated in the verbose log.
Back when I used the WixStdBA and a BAFunction I could step into the Engine
functions using WinDbg (a long time ago now), but I have not found a way to
do that running my mba on a test box (which is network isolated from my
development system so R
I have been reading the wix source code for ideas. I do not really
understand what a Forward Compatible bundle (in contrast to or in
relationship to a Relate bundle.)
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/3-9-702-Bundle-update-behavior-t
Removing the ReleatedBundle Action='Detect' from the bundle, and repeating
the experiments on Bundles A-D does not change the behavior. With Wix
3.9.702 the version designated in the atom feed is ignored if there are
intermediate 'related' bundles cached, but not installed on the local
system.
I will plan to post a bug tomorrow at work. I do not have a wix build
environment for wix 3.9. I tried both at work and at home and have not been
successful yet. I previously built debug versions of wix 3.7 and 3.8 but
still working to get a debug version of wix 3.9. I have been reading the
3.
Sorry for prior post. I did not see Sean's post. Thanks for the assistance.
Should I still post a bug?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/3-9-702-Bundle-update-behavior-tp7595761p7595811.html
Sent from the wix-users mailing list arc
I create a bug here:
http://wixtoolset.org/issues/4472/
Please let me know if more or different information would be helpful.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/3-9-702-Bundle-update-behavior-tp7595761p7595814.html
Sent from the wix-us
Sorry for the double post.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-Show-Hide-a-Text-Control-on-Server-Installation-tp7595834p7595841.html
Sent from the wix-users mailing list archive at Nabble.com.
--
This blog should help:
http://robmensching.com/blog/posts/2008/11/3/how-to-determine-if-you-are-installing-on-windows-client/
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-to-Show-Hide-a-Text-Control-on-Server-Installation-tp7595834p7595840.h
The approach that I used, (some time ago before I switched to using a mba),
is (as I recall)
1) Define a string variable in your Bundle and make it overridable-'yes'.
2) In the localization file define a sting which uses that string variable.
[svWelcomeMessage]
3) Make a copy of the BAFun
I apologize for not reading your question carefully in the other thread. Did
you try to set CustomAction/@Impersonate="yes"?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/MSI-runs-an-EXE-and-it-cannot-write-to-a-file-in-programdata-folder-in-win
Look at the examples at https://wixextba.codeplex.com/documentation
The code at this site was downloaded for wix 3.7, but for wix 3.8 and later
most of it is available by using the built in features and the sample
BAFunctions project. Implement code in the BAFunctions project to detect
the prerequ
I don't understand what is meant by:
"If I add new project in existing project where I add reference of other
project to create msi path, its not compiling and giving mentioned error. "
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperA
Until now I have always used the MediaTemplate EmbedCab='yes". My projects
in general are posted to a web site and I use a mba to update the bundle and
download the packages. This has been working for many projects using wix
3.8.1128. However I have recently experimented with creating these same
On a different question (than my other post about signing external ab files),
when using the MediaTemplate element in an MSI I understand that it will do
'smart cabbing' and create multiple cab files using the CabinetTemplate (or
default) as needed.
So when this MSI is added to a bundle, I assume
Thanks! I'm good at making things harder than necessary
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-external-cabs-tp7595978p7595983.html
Sent from the wix-users mailing list archive at Nabble.com.
--
So if you have a Visual Studio Solution file, and each project that you want
to reference has been added to that VS Solution file, then you add the
reference to your project and use the variables as documented here:
http://wixtoolset.org/documentation/manual/v3/votive/votive_project_references.html
Thanks for the correction. I will have to review where I got the erroneous
idea from.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperApplicationData-attribute-is-not-declared-tp7595444p7596020.html
Sent from the wix-users mailing list
I had a bundle with multiple msi packages installed on a test system (built
with installed wix 3.9.702 on build system).
I installed the wix 3.9.720 on build system this morning, an only rebuilt
the bundle. When I moved it to the test system, which had the prior version
of this product installed,
I transitioned my mba code to model the WixBA UpdateViewModel code in wix
3.9.720. Initially it detected the latest new update and appeared to work
as expected. However the more I play with it I seem to run into a problem
multiple times. I am still a little unsure of how I get to this problem,
b
I have been trying to get the logging.
On my test PC I can only get setups created with the Release build of wix
3.9.720 to run, so when using the test box I tried to add log messages to
each of the three handlers, but in this situation it seems that DetectUpdate
is never fired. (As indicated b
I have not been able to collect any more information on the scenario where
the feed download by the bundle indicated a higher version number, but the
bundle reported 'up to date'. I have not duplicated that scenario on
several systems since this morning, so I am going to let this issue cool its
he
If I add a call to Engine.SetUpdate in mba DetectUpdateBegin, as done in the
past, when this call returns successfully, the DetectUpdateBeginEventArgs
e.UpdateLocation not accessable. Any attempt to log this value causes an
exception, the thread terminates and DetectUpdate handler is never called.
OK. Thanks for the clarification. I will look at that.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/OnDetectUpdateBegin-call-to-SetUpdate-causes-exception-Assert-tp7596059p7596063.html
Sent from the wix-users mailing list archive at Nabble.com
Check out:
http://www.joyofsetup.com/
for changes in VSExpress support.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/WIX-environment-variable-missing-from-Windows-8-1-tp7596093p7596112.html
Sent from the wix-users mailing list archive at Nabble
I would appreciate some assistance in understanding the use of 'custom bind
variables'. From this link:
http://wixtoolset.org/documentation/manual/v3/overview/light.html
"You can create your own binder variables using the WixVariable element or
by simply typing your own variable name in the follow
since the variable is defined as a string, you need to add quotes around the
value that you are comparing the string too. I prefer to use html entities,
but you might prefer a different approach.
InstallCondition ="AToInstall="A""
If the variable were defined as a numeric, then the syntax is as
Thanks! I had the WixVarible in a fragment with no reference to it. But
after moved it as a child of Product, I still have the same error.
While looking for a solution to this problem I refactored my wixlib code and
eliminated most of the places that I was trying to use a bind variable. But
I
Thanks!!! I found the solution to my problem. I changed to using:
!(wix.VariableName)
Maybe I misunderstood the above chm. But I really appreciate figuring out
how to do this, and all of the assistance!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabb
The functionality is a MSBuild feature, which VS uses, to 'batch process'
cultures in the wix linking/binding process. I use batch scripts to to call
MSBuild for each platform specific build of my driver projects. You could
create a MSBuild targets file (much like the wix source does) which calls
Did you try to use util:RegistrySearch for that issue?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-bundle-EXE-setting-property-tp7595178p7596182.html
Sent from the wix-users mailing list archive at Nabble.com.
---
A search of the wix source gives this example:
.
InstallCondition='VS2013InstallFolder OR
VS2013WDExpressInstalled'
If for some reason the above approach is not useful,then:
In the Bindle declare a variable: (also from the wix source, but make it
'Overrideable='yes
In the Bundle element, or a referenced fragment, use a Variable element and
use Override='yes'
or
For control logic in InstallCondition I prefer numeric, but if the variable
is to be passed to MsiProperty use a string.
In the mba, in OnDetectComplete (or wherever you want after Burn ini
In regard to the above discussion about your mba code, I was recently looking
at similar code in the wix src\Setup\WixBA\InstallViewModel.cs which has the
following code:
private void PlanPackageBegin(object sender,
PlanPackageBeginEventArgs e)
{
if
(WixBA.Model.Engine.
When I say that it 'worked' I mean on a Windows 8 x64, with build in netfx4x
support, the mba runs and NetFx40 setup is not launched. On Windows 7 x6x
with no NetFx support installed, the mba prereq dialog prompts the user to
allow NetFx to be installed, then it is installed and my mba is then
lau
I also removed:
And it seems to work without running NetFx on a system that has Fx support.
But I need to test this more next week.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Passing-Variables-from-C-custom-BA-to-WIX-tp7596113p7596194.htm
No, I never found a solution to this problem. I reverted back to using
embedded cab files, which avoided the problem, for now.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/wix39-signing-external-cabs-tp7595976p7596202.html
Sent from the wix-use
There is no such thing as a 'Burn custom action' (and it would be overkill if
it existed). I suggest that you try the built-in functionality of
util:RegistrySearch and using the variable in the Install condition.
If it does not work for you, then post the relevant sections of code and a
verbose l
>>I am wondering if it is possible to use Heat twice in one project.
A MSBuild target is only called once.
In one project I need to harvest files from different source locations. I
define MSBuild Targets with appropriate properties and in each I call the
HeatDirectory Task (not target). The
301 - 400 of 790 matches
Mail list logo
