ASCII (the One True ASCII, ANSI X3.4-1986) is the 7 bit subset of both Windows
"ANSI" and Unicode. In UTF-8 encoding, this subset is a 7-bit value, so ends up
in a single byte which makes it identical to the ASCII and "ANSI" encodings.
The top half of Windows "ANSI" (values 128 to 255) does not
OK, be aware that the check only works in an msi not a budle...
Quoting Devin Morrow :
>
>
> eyoung100 wrote
>> Is the fragment PropertyRef supposed to be commented out...? The
>> Condition Fails if the Id is commented...
>>
>> Carter
>
> I've been playing with this code for awhile now, so some
This doesn't work on 64 bit systems as the ocx file id 32 bit only,
therefore you need SysWow, which as stated previously, is not
inserting...
Quoting Alasdair King :
> MSINET.OCX: either install it to the System32 folder and register it, or
> use RegFree COM. RegFree COM is a great technolog
eyoung100 wrote
> Is the fragment PropertyRef supposed to be commented out...? The
> Condition Fails if the Id is commented...
>
> Carter
I've been playing with this code for awhile now, so some of it is commented
out as I try new things. I was never able to get it to work though, the
messag
MSINET.OCX: either install it to the System32 folder and register it, or
use RegFree COM. RegFree COM is a great technology that makes VB6 programs
really portable: you have to add the entries for the DLL and OCX files to
the manifest for the executable, and then they work magically without any
reg
"Is not inserting in the syswow" folder doesn't really help much. If
you can't copy it there, then you can't register in in HKLM either,
---
Phil Wilson
On Fri, Jun 13, 2014 at 10:33 AM, Carter Young wrote:
> 1. It's my understanding that WiX preferred method is not to save to
> GAC
This might work, the custom action part:
http://msdn.microsoft.com/en-us/library/aa368791(v=vs.85).aspx
I have a vague memory that I did it once for an uninstall, sequence
the CA as soon as you can in the execute sequence for the uninstall
case. I think it wasn't all that friendly a user experien
1. It's my understanding that WiX preferred method is not to save to
GAC, but dont quote me on that.
2. That is outside my area of expertise, although I know others will
answer. If your interested please buy
http://www.amazon.com/WiX-3-6-Developers-Windows-Installer/dp/1782160426
It has sa
eYoung I am able to resolve my problem because of windows security issues it
is not inserting in syswow folder so that's the reason it is not registering
in regedit with syswow folder.
I just added
it worked.
I have few more questions about .net assemblies which should be saved in gac
folder
Is the fragment PropertyRef supposed to be commented out...? The
Condition Fails if the Id is commented...
Carter
Quoting Devin Morrow :
> I'm still really very stuck on this. Can anyone at least point me in the
> right direction?
>
> Thank you!
>
>
>
> --
> View this message in context:
>
I'm still really very stuck on this. Can anyone at least point me in the
right direction?
Thank you!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Setting-up-net-version-check-and-halting-install-tp7595176p7595240.html
Sent from the wix-users ma
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://
The msiexec command line is what it is, it belongs to Microsoft so you
can't invent a new format because you don't want the existing one.
It's normal to have a command line something like ACCEPTEULA=Yes where
ACCEPTEULA is the property you invent to mean that the agreement is
accepted. There's typi
Darn, my apologies... Could he bundle the check in the first MSI in
the bundle??
Carter
Quoting Sean Hall :
> No, that page is for MSI's. The WixNetFxExtension does not currently
> provide a way to detect .NET 1.1 in a bundle.
>
>
> On Fri, Jun 13, 2014 at 9:17 AM, Carter Young wrote:
>
>> S
No, that page is for MSI's. The WixNetFxExtension does not currently
provide a way to detect .NET 1.1 in a bundle.
On Fri, Jun 13, 2014 at 9:17 AM, Carter Young wrote:
> See Step 4:
>
>
> http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/check_for_dotnet.
See Step 4:
http://wixtoolset.org/documentation/manual/v3/howtos/redistributables_and_install_checks/check_for_dotnet.html
Carter
Quoting froggie :
> Hi!
>
> I'm trying to detect if .Net Framework 1.1 is installed and then skip it
> in my bootstrapper. But the setup of NetFx1.1 is always starti
Hi!
I'm trying to detect if .Net Framework 1.1 is installed and then skip it
in my bootstrapper. But the setup of NetFx1.1 is always starting and
then crashing because it is already installed. Can you help?
I have a reference to the netfx-extension and util-extension.
Here is the relevant? code-
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
That is definitely doable in a custom BA. You might want to look here:
http://neilsleightholm.blogspot.com/
Neil has done some work customizing BA's.
--
John Merryweather Cooper
Build & Install Engineer - jXchange
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x7
yes, it doesn't need to be an tree..
The main msi have just main node+node if one want to exclude installation of
shortcut on the desktop.
the other three msi's only have one feature, so the selection in the bundle
would only be to select if one want to install all services and the client,
or onl
Feature selection can be done in a custom BA.
However, applications with Features are often over segmented. For example, I
have a product that has six features, but in reality it is always installed in
one of three sets of those features. The Feature-Tree actually makes this
harder requiring
It seems that with an Bundle, one cannot have feature selections?
So that one cannot choose to install some of the included packages?, that
limits the usage somehow..
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Main-MSI-with-sub-msi-s-tp759522
No, that would have been WiX 3.5. Bundles work just fine since WiX 3.6.
Nested MSI's on the otherhand have officially NOT been supported by the Windows
installer Service for quite awhile.
Burn was designed to address your problem and is the proper tool to solve it.
--
John Merryweather Cooper
B
scubasteve2 wrote
> A bundle can contain a collection of executables, MSIs, MSPs. They can
> all be compressed within the bundle. Read up on Burn and WixStdBA and
> WixManagedBootstrapper.
Ok, but an bundle itself will be an Exe-file right?, not an MSI?
Will read more about this, I was not sure
I found an small issue when I was building msi for IIS application, when you
include WixIIsExtension, and you set your culture to say, "nb-NO", then I
was getting lots of errors like this:
error LGHT0102: The localization variable !(loc.ConfigureIIs) is unknown.
Please ensure the variable is defi
A bundle can contain a collection of executables, MSIs, MSPs. They can all be
compressed within the bundle. Read up on Burn and WixStdBA and
WixManagedBootstrapper.
Stephen Tunney
Nuance Communications, Inc.
Solutions Architect, Imaging Division
Waterloo, Ontario, Canada
stephen.tun...@nuance.
I'm creating four MSI's now, three MSI's are setting up each an WebService,
and, one main MSI that installs an clientapplication.
Today, these are separate MSI's, and will probably be that for those who
want to install separately.
But, the main MSI, we want to be made so it includes the other MSI'
This example:
http://wixtoolset.org/documentation/manual/v3/howtos/files_and_registry/create_start_menu_shortcut.html
If one takes that example, and changes it a little, Allusers=1 and HKLM in
registrykey for the shortcut component
http://schemas.microsoft.com/wix/2006/wi";>
*
Hi all,
In the interactive mode, user needs to accept end-user license agreement by
clicking on the checkbox, which is fine. I have now the silent installer where
I want to have a command line parameter which indicated that the user accepts
the end-user license agreement when the parameter is us
I use melt but without the bindpath the wixpdbs can't find the location on the
new machine where the patches are being built. I'm referring to a build system
where the machines are all based off of the same template but aren't truly
homogenous. Different jenkins slaves have more or fewer execu
Americans don't notice this, but the Norwegian language have some letters
in ASCII, æøå, and those render ok in normal ascii files, but if the file
is UTF-8 they are encoded as unicode in the files (16bit), whereas the rest
of the text in the file is 8bit.
On Fri, Jun 13, 2014 at 9:53 AM, Rob Men
I always get this mixed up but I thought that ASCII was basically a subset of
ANSI and UTF-8 and they all look the same (unless you write a BOM) until you
use non-ASCII characters. The grand majority of internal WiX goo is ASCII
without a BOM so it all looks the same...
I think Joel agrees with
Why? These are internal implementation details to the WiX toolset. If you want
to spelunk the internal file format you would be best served using the API out
of wix.dll.
___
FireGiant | Dedicated support for the WiX toolset |
http
Melt? http://www.joyofsetup.com/2013/07/16/easy-pure-wix-patching-with-melt/
___
FireGiant | Dedicated support for the WiX toolset |
http://www.firegiant.com/
-Original Message-
From: Tunney, Stephen [mailto:stephen.tun...@
34 matches
Mail list logo
