Hi,
I't's in the featue, as follows:
Feature Id=ProductFeature Title=ConnectorMsi Level=1
ComponentRef Id=Salamander.Host.exe/
/Feature
Cheers
Sean.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 13 March 2013 05:37
To: General
No no, you got me all wrong.
I don't want cumulative patches! The opposite, I want the last patch that I
install to supersede all others, overwriting the files.
I have the MSP file and in z7 I can see that it has all the right files, that
is the new files. But if I install it after I installed
Did you increase the assemblyfileversion of those dlls?
-Original Message-
From: Tomer Cohen [mailto:tome...@qualisystems.com]
Sent: 13 March 2013 13:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed Bootstrapper - Second Patch does not
No... there is nothing in the documentation about that...
Won't it make the .NET stop working, the assemblies are signed... if some are
not in the same version, it won't find them...
Thanks for the fast reply. :)
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent:
Just to be clear, the files don't have a newer version, but they are different
in size and binary...
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: יום ד 13 מרץ 2013 16:04
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Managed
You can alter the AssemblyFileVersion without changing the Assembly version,
if you don't have this specified in your AssemblyInfo.cs it will be set to
the same as the assembly version.
e.g.
we bump the build part of assembly file version automatically each build but
assemblyVersion is
If the Feature is under the Product element somewhere then I'm at a loss as
to what is actually going wrong. It seems like everything should work. What
is the exact command-line and output you are getting from the tools?
On Wed, Mar 13, 2013 at 1:46 AM, Sean Farrow
What does the verbose log file in the patch say the action states for the
Components that you expect to be installed? Also, look at the File install
log lines, those usually have quite a bit information about when the file
is being applied and whether it is being patched.
On Wed, Mar 13, 2013 at
You can put multiple .wxl Payload files in your Bundle. If you have
Payload/@Name=1041\thm.wxl then that .wxl will change the strings in your
thm.xml when the user language is set to Japanese. There is no option for a
drop down to pick today. If you want to persist the value, you could pass
the
Yeah, that documentation is pretty bad. Feel free to file a bug. I'm not
even sure what it is trying to say.
On Mon, Mar 4, 2013 at 6:43 AM, keith.doug...@statcan.gc.ca wrote:
Following up on my own previous post,
The description of Permission has this line in the documentation:
PerfCounter was deprecated a long time ago when Vista came along, I
believe. My memory may be a little fuzzy. I think it has something to do
with lodctr being no longer the recommended way to install perf counters by
MSDN.
Ultimately, if there is a problem in PerformanceCategory and friends, then
Hi,
Thanks for the reply.
I have this in my log, this is the log of the second patch installation. The
MSP itself has all assemblies, but only installs those files below.
Patch Modified Files List:
MSI (s) (C4:04) [15:51:46:984]: File =
QualiSystems.ResourceManagement.Service.Plugin.config:
What does the action state for the *Components* show? That's what the
Windows Installer is basing it's decision on. It would root cause the
issue. It very likely could be the version of the files not changing but it
would be best to *know* what fixed it, right?
On Wed, Mar 13, 2013 at 8:18 AM,
Hi,
I'm also having some issue with this with VsixPackage. I can build the
installer fine but when it runs I get an error.
I have installed latest Wix. Does this wxs look ok?
?xml version=1.0 encoding=UTF-8?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
That error means the VsixInstaller failed. Doesn't the VsixInstaller create
a log file somewhere? That's your best bet.
On Wed, Mar 13, 2013 at 8:25 AM, Thomas thomas.wu...@hotmail.com wrote:
Hi,
I'm also having some issue with this with VsixPackage. I can build the
installer fine but when
What more information would you like about the feature? Also, why would
you want to turn it off? Other projects types do not let you turn off their
incremental build facility. What could have been done better (other than
just have it auotmatically work, which was the intent smile/)?
Very
In WiX v3.7 (and maybe all of WiX v3.7+) the Update/@Location really is
just information provided to the BootstrapperApplication. Basically if you
have an update location, the engine will say, Hey, BA, now would be a good
time to use this string and figure out if there is an update. Technically
See this:
http://msdn.microsoft.com/en-us/library/ee332502.aspx
Apparently it's a bad idea to run VSIXInstaller from an MSI.
On 13 March 2013 15:31, Rob Mensching r...@robmensching.com wrote:
That error means the VsixInstaller failed. Doesn't the VsixInstaller create
a log file somewhere?
Hi Rob, and thanks for your reply.
robmen wrote
Want to help us fix the root issue? If so, love to start a discussion on
wix-devs@.sourceforge
about the best way to fix the targets to correctly handle the situation.
First off, I tried answering via the [hidden email] link, but then I get
I had problems with installing VSIX from msi too and eventually read that you
should install 'by hand' if you are using MSI.
There is some very helpful code in the wix installer itself to help you with
registrations etc.
-Original Message-
From: John Ludlow
I don't use Nabble. I join via here:
http://wix.sourceforge.net/mailinglists.html. I know that works. smile/
This conversation is better for wix-devs, short answer: no WiX does not
create those files. The mergemod.dll from the MSI SDK creates those files
so we're going to have to be more creative
Does the Visual Studio plugin for WiX 3.7 have logic for selecting the
correct platform-specific reference when building both 32-bit and 64-bit
configurations so workarounds like
http://stackoverflow.com/questions/8713683/installing-32-64-bit-drivers-with-wix
are unnecessary now?
For example
...and to exapand on that, look for your files in the log. There should be a
FileCopy that will say something like Won't Overwrite;Won't patch;
and give you a reason.
If your patch is incorrect because of component rules, look for SELMGR in
the log and any remarks about removing
WiX doesn't make a habit of documenting (duplicating) Windows Installer
docs. These are the update rules for versioned files:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa367835(v=vs.85).as
px
And you are probably confusing AssemblyVersion that's used for client
binding with
I have a solution with a Wix Boostrapper project, and several other c++/c#
projects. The Boostrapper project, the project that creates the EXE file,
cannot be set to be the startup project. Although the solution compiles and a
setup.exe gets build, nothing happens when I run the setup.exe.
Hi:
This is sorted, I had a stray fragment at the bottom, and didn't see it!
Sean.
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: 13 March 2013 15:08
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] issue with fragments in
So I did you get the Wix3.6 bundle to know 3.7 exists and to fetch and execute
it?
Is it going to be code in the BA? A property I can detect?
It seems like it will work to always execute a setup.exe from the same URL and
just keep replacing it with an updated version that gets the latest
I implemented auto update in the extended BA (http://wixextba.codeplex.com/) I
am not sure it is the best way to do it but it works. Check out the discussion
on the site for information on how to use it. There was also a recent discuss
on wix-devs about it.
On Tue, Mar 12, 2013 at 1:31 PM,
Yes, behavior should have been like you sad.
I`m sorry, I didn't know the minor udate rules.
Changing some components guid (autogenerated by heat) and changing file
locations of the same components did cause of my problems.
Thank you.
Best regards, Alexey.
--
View this message in context:
Ok, I see that on http://wix.codeplex.com/releases/view/93929 there is a zip
file that contains source. What is needed to build the wix 3.6 toolkit?
Can I build it using DevStudio 2010? Is the source complete?
I tried to open the wix.sln (which my machine says it is 2010 sln file, but
it
The BA does the look up, there is nothing built into the engine (as of yet)
since there are so many ways to do it. smile/
The question is do you want people that are installing an old setup.exe to
know that there is a newer one available? That's what the Bundle Update
does.
On Wed, Mar 13, 2013
Not today. You can build the bootstrapper project but there are no
debugging/launch features built into Votive. So all that F5 related stuff
doesn't do anything.
On Wed, Mar 13, 2013 at 9:58 AM, George Fleming gef...@microsoft.comwrote:
I have a solution with a Wix Boostrapper project, and
You need to enlist in the Mercurial repository to build. The sources.zip is
availble for debugging purposes (along with the pdbs.zip) it is not
buildable. To build wix36, you use make.bat. It requires lots of stuff
installed on your machine to build correctly.
On Wed, Mar 13, 2013 at 11:07 AM,
That or a embedded UI would need to be implemented in the WiX toolset.
Personally, I jumped over that feature and went for the full blown
bootstrapper/chainer with Burn... but GPO functionality does suffer a bit.
Might be an interesting feature to implement in the future to provide a
stock
So any tip on how I can debug my problem? My Setup.exe doesn't seem to do
anything (it just silently returns, with no screen pop up). Is there any way
to invoke logging, like with msiexec?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Wednesday, March
Hi all,
I have a Custom Action DLL (C#)
Within the Welcome page to the ready to install page I have been able to
populate a MSI Property for any error messages/exceptions that are caused by
the Custom Action calls..
i.e.
At beginning of the Custom Action method:
SetSessionProperty(session,
OK, I found the log file in %TEMP%. Here's basically what it says:
[127C:12C0][2013-03-13T11:54:57]i001: Burn v3.7.1224.0, Windows v6.1 (Build
7601: Service Pack 1), path: C:\...\Setup.exe, cmdline: ''
[127C:12C0][2013-03-13T11:54:57]i000: Initializing string variable
'InstallFolder' to value
The compiler recognizes the UI element in the WixLocalization schema that
allows a localization to override the position, size, and text of dialogs
and controls. The WixStdBA also supports this WXL feature however the
corresponding element is named Control instead of UI. Is this
difference
OK, Thanks to Steven for pointing me in the right direction, I now have
a solution that works fine for me. Here's the WiX source:
InstallExecuteSequence
Custom Action=ScriptForInstall After=InstallInitialize /
Custom Action='ScriptForRemove'
Thanks Rob,
So how do I enlist to the Mercurial repository? All I want to do is
compile burn. I want to confirm our static analysis and debugging.
Any direction is appreciated.
-Jon
-
- jon
--
View this message in context:
Try this - it will keep the messagebox on top of everything.
MessageBox(NULL, LPlease click ok to continue., LSetup messageBox title,
MB_OK | MB_SYSTEMMODAL);
--
View this message in context:
This is an area to improve for debugging Bootstrapper Applications. The
error code will help but hard sometimes to figure out all the different
things that can go wrong in a managed BA. I often drop down to do
devenv.com /debugexe path\to\bundle.exe and then start debugging through
the Burn code
I have an Burn app that works with Wix 3.6. The Bundle.wxs looks something
like this:
BootstrapperApplication Id='ManagedBootstrapperApplicationHost'
SourceFile=$(var.WixToolsDir)\Burn\mbahost.dll
Payload SourceFile=$(var.WixToolsDir)\SDK\BootstrapperCore.dll
Just kind of a general question on how to do this. Since my Setup.exe only has
a Setup.wixpdb, and not a Setup.pdb, VS does not allow me to step into it. How
do I utilize pdbs.zip and sources.zip to debug?
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent:
You must have something from very early in WiX v3.6. The correct way to
reference the mbahost is like so:
BootstrapperApplicationRef Id='ManagedBootstrapperApplicationHost'
On Wed, Mar 13, 2013 at 8:58 PM, George Fleming gef...@microsoft.comwrote:
I have an Burn app that works with
Unzip the pdbs.zip and the sources.zip somewhere. Then when VS says it
can't find symbols for your Setup.exe, point to the place where you
extracted the .pdbs, and when VS says it wants a source file point it to
where the sources.zip was extracted.
On Wed, Mar 13, 2013 at 8:59 PM, George Fleming
46 matches
Mail list logo
