It will be fixed. Fredrik has just been busy lately.
On Tue, Oct 18, 2011 at 1:23 AM, Kryschan
christian.hennig@wincor-nixdorf.com wrote:
jhennessey wrote:
The bug is still open, see the submitter's comments:
A lot of Votive code was written to support VS2003. It still supports
VS2005. Very possible that code is left over from all that stuff.
On Mon, Oct 17, 2011 at 12:33 PM, John Bergman
john.berg...@xpedienttechnologies.com wrote:
In Visual Studio 2010, with the latest Wix Installed, I add some
Yes.
On Mon, Oct 17, 2011 at 8:17 PM, Hoover, Jacob
jacob.hoo...@greenheck.comwrote:
While I know I could customize the BA to suite my needs, might I suggest
a slight change to the thmutil.cpp. If a user supplies an
IconSourceFile from within the Bundle, the primary exe file will have a
Yes, That sould all be customizable now.
On Wed, Oct 12, 2011 at 2:09 PM, shruthi02 shru...@live.com wrote:
Hi,
Is it possible to customize and localize the first UI screen that shows up
if BA needs .Net and it isn't installed?
Also, is there a way to provide localized versions of the .Net
Verifying the signature verifies the hash of the file. It allows you to
change the exact file as long as the signature is still valid. The behavior
you see is by design.
I don't understand your comment about failing the local check it should use
the download URL. That is what the wixstdba.dll
Heat has lots of gaps. It's an area for us to invest in WiX v4.
On Wed, Oct 19, 2011 at 10:08 AM, David L. Beckwith
beckw...@interaccess.com wrote:
I'm using Burn and I got to say I love it!!!
However, it makes me want more...
I'm trying to get a legacy installation package chained and am
Not all options are exposed through Votive so sometimes you have to use the
general pass items on the command-line. Ultimately, the wix20??.targets
lists all the options available. The documentation is okay.
On Tue, Oct 18, 2011 at 12:03 PM, John Bergman
john.berg...@xpedienttechnologies.com
CHT and CHS are supported by some code page but I remember Thai being a
problem for someone because it doesn't have a codepage... or something like
that. You can try 65001 (I think that's UTF-8) but it will have issues if
you show any Windows Installer dialogs (wrapping all the UI in Burn could
1. The code could be changed.
2. Would have to see how you're using XmlFile to know for sure. Have you
considered switching to XmlConfig? It may be a bit more robust... I haven't
looked in a while.
3. Yeah, IIS is very annoying like that. It see changes to the files and
starts reading the files
Yep, fallback back to registry keys. Feel free to open bugs for the registry
keys that seem to be missing from the high-level elements. We should
eventually get them all.
On Fri, Oct 21, 2011 at 6:36 AM, bpackard bill.pack...@kepware.com wrote:
I am attempting to create AppId, Class and ProgId
Okay, sounds like something to add to the WiX BA.
On Tue, Oct 11, 2011 at 6:35 AM, jhennessey jack.hennes...@hyland.comwrote:
I always grab the binaries (we check them in) but still use the MSI for
Votive. I have VS2005, VS2008, and VS2010 but only need votive for 2010.
So,
I don't install
Burn does exactly what you ask. It comes in the
IBootstrapperApplication::OnDetectRelatedMsiPackage(). Your BA gets all the
information.
What does not exist is an UpgradeCodeSearch element to create a property
from some discovered ProductCodes.
On Fri, Oct 14, 2011 at 1:29 PM, Tobias S
Yes, that is possible now.
On Thu, Oct 6, 2011 at 11:47 AM, shruthi02 shru...@live.com wrote:
Is there a way to replace the prerequisite .Net install UI with just an
notification to the user that they need to install a particular version of
.Net before they can install the bundle?
Thanks,
13 matches
Mail list logo