Hi All,
I'd like to install my app to %LocalAppData% folder.
Following directory setting worked perfectly for me:
However, when I tried changing "ProgramFilesFolder" to "LocalAppDataFolder", I
got lots of error when using light to link and generate my msi:
D:\runGroup.wxs(53) : error
A .sqlproj is a new project type that can be created after the SQL Server Data
Tools are installed. The new project type replaces the .dbproj project type for
databases. If I understood better how the properties typically flow across the
project references, then I could help figure out why it do
>From what I’ve tested, It’s quite hard to override the FilesInUse and the
MsiRMFilesInUse dialogs.
The problem is that there are already built-in inside Wix, I cannot simply
redefine them in my own .wxi. I kind of gave up after struggling with
errors after errors.
** **
Well, maybe I ha
Yes, I am using the .xml and .xwl theme files to modify prompts and background
colors. The button does become "close" but it does nothing when I click on it.
I have to use the window X for closing.
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, A
Works fine for me. Have you modified the Burn UI? When an MSI is cancelled, the
"cancel" button becomes a "close" button for me.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integra
That's exactly what you'd have to do in this case. Honestly, it's not much
different than what Burn would have to do in this case as well. I dislike
this design for uninstalls.
On Thu, Aug 23, 2012 at 8:17 AM, Hoover, Jacob
wrote:
> I really don't like this approach, but in theory could you not
I'd also recommend using the MajorUpgrade element to upgrade your MSIs.
That's the "proper" way to upgrade.
On Thu, Aug 23, 2012 at 9:02 AM, Alec Swan wrote:
> You are spot on! We were using NullSoft product. I just closed the thread.
>
> Thanks!
>
> On Thu, Aug 23, 2012 at 9:55 AM, Peter Shirt
I have tried to follow the examples I have been able to find regarding Burn and
installing an MSI as part of the chain. I have an MSI that has its
DisplayInternalUI set to yes.
If the user cancels the MSI install, burn shows that it failed (fine) but the
cancel button on the window no longer wo
You are spot on! We were using NullSoft product. I just closed the thread.
Thanks!
On Thu, Aug 23, 2012 at 9:55 AM, Peter Shirtcliffe wrote:
> An MSI installer will always have the product code GUID in the key, exactly
> as you have there. Were you using InstallShield or something before ?
>
> -
After some internal discussions it turned out that we were looking for
UnistallString to support upgrade from our product version that used
to be installed with NullSoft to the version that is currently
installed with MSI.
I am closing this thread, sorry for the confusion.
Thanks,
Alec
On Thu,
An MSI installer will always have the product code GUID in the key, exactly
as you have there. Were you using InstallShield or something before ?
-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com]
Sent: 23 August 2012 16:34
To: General discussion for Windows Installer XML tool
Actually, I just found that
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{5D6E0940-C1EB-4C60-8A36-54D6BCCF5C02}
contains an UninstallString for our product. Now I have to track down
how we ended up with a GUID in this reg key because it used to be the
name of our product.
We can still uninstall the product from Add/Remove Programs but there
is no entry for our product under
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
reg key. Is it possible UninstallString is written in some other
registry location?
Thanks,
Alec
On Thu, Aug 23, 2012 at
Good idea, I'm going to look into this approach and post back if I'm
successful...thanks for the idea!
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-InstallAnywhere-ExePackage-tp7580040p7580050.html
Sent from the wix-users mailing list archi
I really don't like this approach, but in theory could you not create a Stub
EXE that would take an install or uninstall parameter and would have to have
the knowledge of the InstallAnywhere package? You could then bundle this stub
with your InstallAnywhere package.
-Original Message-
Sounds like an strange design. Normally you'd make a major upgrade to remove
the old version automatically and replace it with the new one. Any data that
needs preserving is probably configuration or user data and should be handled
by the application rather than the installer. The normal way to uni
Yeah I have never even been exposed to this type of installer until very
recently. Should I file a bug for 3.7 to track this?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-InstallAnywhere-ExePackage-tp7580040p7580047.html
Sent from the wix-u
It is poorly documented but it does exist and exists for this very sort of
reason.
The file is always right next to your BA.dll. Unfortunately, the WixBA
doesn't need any information from the file so I can't point to it as an
example how to load the file.
Just get the executing path of your BA.dl
Yeah, sadly we totally missed this pattern of exe installers in the first
version of Burn.
On Thu, Aug 23, 2012 at 7:41 AM, jhennessey wrote:
> I was wondering if anyone out there has had the unfortunate task of trying
> to
> bootstrap an InstallAnywhere package?
>
> I ask because apparently to u
Just guessing but the ".dll" below in your BootstrapperCore.config could be
a problem:
On Thu, Aug 23, 2012 at 4:59 AM, Adkins, Christopher <
christopher.adk...@docuware.com> wrote:
> Hi,
>
> I have created the bootstrapper in such a way that all the files should be
> include
There is a feature request open to support turning on Windows "roles and
features". It's obviously not implemented yet.
On Thu, Aug 23, 2012 at 5:52 AM, Neil Sleightholm wrote:
> I think that still suffers the same issue, you need to run "ocsetup
> NetFx3" and burn doesn't (and probably shouldn'
It's probably something unique about the .sqlproj that prevents the
variables from flowing across the project references. I've never crated a
..sqlproj. How do you do that?
On Wed, Aug 22, 2012 at 6:17 PM, Castro, Edwin G. (Hillsboro) <
edwin.cas...@fiserv.com> wrote:
> I'm building the .sln in b
wix64.proj can only be called after some of the previous parts of the build
are built. Take a look at wix.proj in the root of the project. You'll see
the overall order.
Still trying to decide how best to create all the cross dependencies
between all the various projects.
On Thu, Aug 23, 2012 at 2
I was wondering if anyone out there has had the unfortunate task of trying to
bootstrap an InstallAnywhere package?
I ask because apparently to uninstall these types of packages you need to
launch an "uninstall.exe" file that gets installed by the setup executable.
That being the case it appears b
We use UninstallString to run the uninstaller when the product is
updated in place.
So, when the user runs our installer the installer looks for
UninstallString reg key and if found the installer asks if user wants
to wipe out previous product version's data or try to preserve it and
then runs the
Hi, Can anyone help me I'm getting errors and my installation is ending
prematurely.
Here are the log files:
Action start 11:06:04: InstallInitialize.
MSI (s) (00:90) [11:06:04:186]: Note: 1: 2205 2: 3: Component
Action ended 11:06:04: InstallInitialize. Return value 3.
Action ended 11:06:04: I
I think that still suffers the same issue, you need to run "ocsetup NetFx3" and
burn doesn't (and probably shouldn't) allow you to run arbitrary applications.
I think I'll need to write a powershell or ocsetup wrapper that I launch with
ExePackage.
Neil
-Original Message-
From: Peter S
A big thanks to Rob and Peter. It worked. You saved my day.
Thanks.
Sudripta.
-Original Message-
From: "Rob Mensching"
Sent: Wednesday, 22 August, 2012 6:00pm
To: "General discussion for Windows Installer XML toolset."
Subject: Re: [WiX-users] Files to install in a location
Also be aware that the feature names for .NET differ between Server and
Server Core.
(Microsoft never makes it easier for us... always more complicated.)
From: "Peter Shirtcliffe"
Sent: Thursday, August 23, 2012 6:59 AM
To: "General discussion for Windo
Hi,
I have created the bootstrapper in such a way that all the files should be
included in the package itself (meaning I have set Compressed="yes" on
everything). I will try getting some more information through ProcMon, but on
first glance it isn't telling me much.
Best regards,
Christopher A
DISM has been mentioned on here before
http://technet.microsoft.com/en-us/library/dd744256%28v=ws.10%29.aspx
It might be worth searching back through the mailing list.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 23 August 2012 12:39
To: General toolset. (wi
Does anyone know how you could use burn to install .NET 3.5 on Windows 2008 R2
(and Windows 8)?
I know you need to use powershell like this: "powershell.exe Import-Module
ServerManager ; Add-WindowsFeature as-net-framework" but can't see how I could
do that with burn. I did think I could copy t
2 different components cannot deploy the same file to the same location.
The best fix depends on how much control you have over the merge module
definitions, whether you've published either of them already, etc. Your
options include:
Remove one of the components entirely.
Remove one of the compon
With a subject this time :)
-Original Message-
From: Aditya Mohan [mailto:amo...@quark.com]
Sent: Thursday, August 23, 2012 4:38 PM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] (no subject)
Hello Guys.
We are creating an installer that uses multiple mer
Hi,
0x80070002 means file not found. Make sure you have your file references in the
bundle correct. You can also use Sysinternals ProcMon to see where the bundle
tries to locate your bootstrapper.
Kind regards,
Henning
> -Original Message-
> From: Adkins, Christopher [mailto:christophe
Hello Guys.
We are creating an installer that uses multiple merge modules. Two of
these modules deploy a particular file at the same location, hence
causing a compilation error.
We can alter only one of the modules.
The error is:
light.exe : error LGHT0204 : ICE30: The target file
'pbsgpqfc.res|
Sorry, I forgot to mention that I also included that. I am not sure what else I
can try and sadly I haven't found any information about that error number
either.
Best regards,
Christopher Adkins
Manager Research and Development
-Original Message-
From: Christoffel le Roux [mailto:christ
Hi, I think you mabe need the following in your Assembly.cs
[assembly: BootstrapperApplication(typeof(Bootstrap))]
Kind regards,
Christoffel le Roux
Software Development Engineer
Finalist: 2011 Microsoft Customer Experience Partner of Year
www.flowcentric.com | Email: christoffe...@flowcentri
Hi Neil, I upgraded to 3.7 to see if it will make any difference to my problem
:), thanks for the help I really appreciate.
Kind regards,
Christoffel le Roux
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Thursday, August 23, 2012 12:31 PM
To: General discus
It might be worth dropping back to 3.6, 3.7 is very new.
Neil
-Original Message-
From: Christoffel le Roux [mailto:christoffe...@tech.flowcentric.com]
Sent: 23 August 2012 10:52 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn CLIENTUILEVEL
Hi N
Hi everyone,
I am trying to get a custom burn UI working, but I can't even get it to start.
I have looked at the WiXUX project as an example, but I am stuck on what I am
doing wrong. The log tells me:
[0428:0BC8][2012-08-23T12:04:17]: Burn v3.6.2928.0, Windows v6.1 (Build 7600:
Service Pack 0)
Hi Neil, I'm on the latest 3.7 build. If I place a breakpoint inside my
IEmbeddedUI implementation the 'Run' method is never hit.
Kind regards,
Christoffel le Roux
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, August 22, 2012 11:09 AM
To: Gener
Windows Installer runs as the localsystem account which doesn't have
permissions on the network so you're probably being denied access to create
the directory. Check the permissions on the share and on the directory.
-Original Message-
From: Osanger, Martin [mailto:martin.osan...@fabasoft.
Thanks, however if I 'msbuild wix64.proj', I get errors as follows:
LINK : fatal error LNK1104: cannot open file 'wcautil_2010.lib'
and then various errors on
"C:\wix3.7.821.0-sources\build\debug\x86\GenerateWixInclude.exe" which
doesn't exist...
please advise,
--
View this message in contex
I'm trying to accomplish something similar with my own Bootstrapper
Application, and would like to find this XML file. What is the suggested way of
locating this file? I'm unsure how to locate my BA DLL at runtime without
resorting to magic strings.
In addition, is there any documentation at al
Windows Installer itself writes the value.
http://msdn.microsoft.com/en-us/library/aa372105%28v=VS.85%29.aspx
However, the uninstall string is not used by Windows Installer so does it
matter that it wasn't written ?
-Original Message-
From: Alec Swan [mailto:alecs...@gmail.com]
Sent: 23 A
Hello,
Are there any restrictions to create a folder which is reachable via UNC Path?
The user can create folders in the Programs directory but the setup can't.
MSI (s) (D4:24) [12:46:14:010]: Executing op:
FolderCreate(Folder=\\ligov\users\UserData\\AppData\Roaming\Microsoft\Windows\Start
Men
You can suppress the FilesInUse dialog by specifying
Dialog@Modeless="yes" and Dialog@Hidden="yes".
Rob
On 23/08/2012 01:31, Gustavo Gustavo wrote:
> I’ve been struggling to get rid of the Files In Use dialog. Seems like
> there’s no easy way out.
>
> Ideally, I would like to execute my MSI
48 matches
Mail list logo
