mmm - i believe i have misunderstood what is happening.
I have tried installing my bundle with MsiPackage 'A' & 3 different versions
of ExePackage 'B'
2 were successfull - indicating that i am wrong in believing that the
version has to be the same as was there when the bundle was built.
1 failed
I have a bundle that installs msi 'A' plus support application 'B'
'A' is an MsiPackage
'B' is an ExePackage
'B' is not compressed - i.e. external payload
My problem is that if application 'B' is updated after i release my bundle,
then that new version is just dropped onto the distribution DVD wi
Rob,
I wasn't in any way implying that WiX was doing anything wrong - I agree
that it is Trend that are causing this. All i meant was i didnt know if 3.7
would be doing something sublty different that wouldnt trigger the 'malware'
alert.
Thanks.
--
View this message in context:
http://wind
I'm not sure whether submitting our product to Trend would have any effect,
since it is /behaviour/ that is triggering the alert, not any 'patterns' in
the setup code itself (if that makes sense)?
I can try this though. Presumably it is the extracted burn setup.exe that
needs to be sent, since th
We had (and still have) issues with 3.6 & Trend Officescan. It objects to
the way that the burn setup.exe is extracted into temp & then writes to the
RunOnce registry key. OfficeScan sees this as malware behaviour & blocks
it. Even though everything is signed.
If you havent signed everything th
For the 1st release of an installer I used this to conditionally install a
component:
i.e. only install ProductFeatures.2 if INSTALL_TYPE = 2
INSTALL_TYPE is passed in from command line / burn MsiProperty.
It worked fine & on uninstall everything gets removed. Great.
But now when v2 went ou
I have a custom managed BA which may need to install Windows Installer 4.5 in
order to install SQL Express (which requires a re-boot).
I have managed to get the re-boot sequence working OK when 4.5 is installed,
& my installer re-starts OK - but it restarts from my first screen, meaning
the user h
ould be removed.
>
> It never occured to me that they may have shipped one of those MSI files.
>
> On Wed, May 9, 2012 at 7:09 AM, stewarth
> <stewart.hilson@>wrote:
>
>>
>> stewarth wrote
>> >
>> >
>> > stewarth wrote
>> >>
>
stewarth wrote
>
>
> stewarth wrote
>>
>> Just trying to add the vc 2010 runtime to my bundle.
>>
>> The installation files available to me on our network are :
>>
>> P:\Projects\Updates\VS2010_x86\vc_red.msi
>> P:\Projects\Updates\VS2010_x
stewarth wrote
>
> Just trying to add the vc 2010 runtime to my bundle.
>
> The installation files available to me on our network are :
>
> P:\Projects\Updates\VS2010_x86\vc_red.msi
> P:\Projects\Updates\VS2010_x86\vc_red.cab
>
> (not sure why we dont just use vcre
Just trying to add the vc 2010 runtime to my bundle.
The installation files available to me on our network are :
P:\Projects\Updates\VS2010_x86\vc_red.msi
P:\Projects\Updates\VS2010_x86\vc_red.cab
(not sure why we dont just use vcredist_x86.exe...)
I add these to my bundle as:
stewarth wrote
>
> Using Burn, my setup generates 2 log files, one from the bundle and one
> from an msi.
>
> If my install fails, i'd like to display some sort of 'see this log file:
> logfilename' so users will know what to send to us, and during test i don
Using Burn, my setup generates 2 log files, one from the bundle and one from
an msi.
If my install fails, i'd like to display some sort of 'see this log file:
logfilename' so users will know what to send to us, and during test i dont
have to keep reminding people where to look (!)
So, from my BA
Hi -
I have set protocol="netfx" for the .Net 4.0 ExePackage, and i do get a
moving progress bar during its installation. However i wonder if there is a
way of showing what the .net installer is actually doing because this can
take ages & still looks at times like it has hung.
I use [ProgressPa
I am currently out of the office, returning Monday 16th April.
This e-mail is for the sole use of the intended recipient and contains
information that may be privileged and/or confidential. If you are not an
intended recipient, please notify the sender by return e-mail and delete this
e-mail
I have pretty much completed our burn mba installer but just come across a
slight problem.
I have declared the .Net 4 ExePackage as compressed="no" (along with all our
other pre-reqs, i.e. SQL Express etc) to avoid sucking it into every build
that we do during test. I have a resolver in my mba th
I'm dont know if I'm posting correctly because no-one seems to look at my
posts .
Anyway - i resolved this issue. I needed to set the
ResolveSourceEventArgs.Result to Result.Retry.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Can-t-get-SetLocalS
I got this working by adding my image file to the payload -
& in the .thm file:
Also, in case anyone is scratching their head like i was with localisation,
you need to define two WixVariables:
Otherwise it will use the default ones.
--
View this message in contex
18 matches
Mail list logo
