On 11/05/2012 19:22, Elliott Dicus wrote:
Do I need
to be doing something like:
Component Id=MyDriver Guid=[PUT GUID]
Driver Legacy='yes' /
File Id=cyusb.inf Vital=yes /
/Component
and using DIFxApp?
Yes, I'd say you're best off using Difx.
Rob
I think you should also be including all driver files (inf, sys, dll, readme
etc.) In a single component.
--
Bruce Cran
On 11 May 2012, at 19:22, Elliott Dicus ewdi...@gmail.com wrote:
Hello all,
I'm working on a project that communicates with an Arduino Uno. As such,
we'd like to
Sorry Rob I was off ill last week so haven't seen this message until now.
Basically it was working as expected in v3.6.2830.0 earlier but as of
v3.6.2907.0 it just doesn't even attempt to try to sign the bundle when
building using Visual Studio 2010.
Here's my bundle .wixproj in full
?xml
I'm kind of suprised with Rob's answer. Can you write an install in WiX
that does a minor upgrade of an installer written in IS? Perhaps. It'd
have to be very careful coding to keep all the primary keys and components
the same and get the media built the same way. I suppose it's
I need to perform certain action on my checkbox.
At the start if the installation the chkbox is disabled. There is a button
to call a custom action and verify certain things and assign a value to a
variable.
This variable will decide whether to enable chkbox or not. I have
implemented till this
I forgot to put down that
C:\Windows\system32\\bcdedit.exe /set testsigning on - worked on a command
line that was run as administrator
but not in the quiet custom action during the install.
--
View this message in context:
Yes, that's correct. I was also looking at this and came across this blog:
http://kobyk.wordpress.com/2008/10/21/installing-filter-drivers-with-difxapp-and-a-wix-v3-msi/
Wes
-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: May-14-12 7:00 AM
To: General discussion
Also you need to create one MSI for both x86 and x64 I think. Reference
difxapp_x86 in one and difxapp_x64 in the other. Reference WixDifxAppExtension
in both.
Wes
-Original Message-
From: Bruce Cran [mailto:br...@cran.org.uk]
Sent: May-14-12 7:00 AM
To: General discussion for
The log you sent did not show this command line (with the quotes) as the
command that executed. If you did in fact change your MSI to remote the extra
quotes and you can see in the log that they are no longer there and it still
didn't work then you have an interesting issue to resolve. In that
Nice, thanks Rob =)
I may have just missed this on the web page as I switched to Chrome recently
which doesn't have any built-in RSS detection like Internet Explorer (I now
have an extension installed to do this though).
Cheers,
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945
Hello!
I'm developing my own bootstrapper app and I have an exe that needs a txt
file in the same folder to be able to run. I have defined it in my bundle
like this:
ExePackage Id=TTUpdate PerMachine=yes
SuppressSignatureVerification=yes
SourceFile=C:\TTFiles\setversion.exe
On 11-May-12 04:53, Gareth wrote:
Hi Bob, thanks for your input, but why would it ever be necessary to include
32-bit merge modules in a 64-bit package?
When you have a 64-bit component like a shell extension but everything
else is 32-bit. MSI doesn't support a 32-bit package with 64-bit
We have a need to install additional files when doing a patch. As a result
patching a patch requires access to original source.
Is it possible to have patch install new files without access to original
source?
--
Live
What do I need to remove to repair a damaged OS package database? Ie. if
uninstall from Add/Remove programs fails, what do I do manually to manually
remove the package from the database? (I can manually delete the package
itself, of course.)
Is it sufficient to remove the package's cache
You should get a ResolveSource callback for every missing payload. Can you
share a log file that shows that not happening?
On Mon, May 14, 2012 at 11:08 AM, Miss Parker caisa.westl...@gmail.comwrote:
Hello!
I'm developing my own bootstrapper app and I have an exe that needs a txt
file in the
If you add all the new Components to a new Feature that does not cause any
of your other Features to repair, it should work. Verbose log file should
show you where things are going awry.
On Mon, May 14, 2012 at 1:49 PM, Alex Ivanoff aivan...@vmware.com wrote:
We have a need to install
Best thing is to uninstall all of your MSI files (msiexec /x {PRODUCTCODE})
then try uninstalling the Bundle. That (almost) always works and cleans up
everything completely.
On Mon, May 14, 2012 at 3:16 PM, Kenneth Porter sh...@sewingwitch.comwrote:
What do I need to remove to repair a damaged
Did not help.vOne thing noticed is that NewFile.dll sequence in File
table is 1 (patch media id is 5000). Is this correct?
And here is the part of the log:
MSI (s) (DC:A4) [22:56:38:532]: File: C:\Program Files
(x86)\Company\Product\NewFile.dll; To be installed;Won't
patch; No
Hi WIX people,
Is there any way to get more information when a path is supposedly
empty? I've looked at all my paths and they look fine, and it would
really help to be able to narrow down WHAT file/directory is missing!
WIX pops out with the most astonishing errors sometimes, e.g.
How are you building your patch?
On Mon, May 14, 2012 at 9:14 PM, Alex Ivanoff aivan...@vmware.com wrote:
Did not help.vOne thing noticed is that NewFile.dll sequence in File
table is 1 (patch media id is 5000). Is this correct?
And here is the part of the log:
MSI (s) (DC:A4)
Using WIX-only approach.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Monday, May 14, 2012 23:34
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] New files in patch and original source
How are you building your patch?
On
Hi,
Ok, I didn't get a ResolveSource for the text file, only the exe, but
according to the log it found the file anyway. Perhaps Burn uses the exe
packages new path by default for the internal payloads?
Unfortunately the exe didn't use the text file during execution and failed
to write to
22 matches
Mail list logo