Thanks Blair.
That did the trick.
I was trying to use element in the HarvestFile
command/element but this didn't work.
Graham
-Original Message-
From: Blair Murri [mailto:os...@live.com]
Sent: 24 January 2014 06:04
To: General discussion for Windows Installer XML toolset.
Subject: Re
Share the contents of your config file for your BA
It is probably telling the stdba that you work with 3.5 so it doesn’t run the
prereq on win7 (since 3.5 is included in win7), then the load fails because you
require 4.x.
Blair
From: sky
Sent: Thursday, January 23, 2014 10:
Add -svb6 to the
first in your WIXPROJ.
Blair
From: Graham Allwood
Sent: Wednesday, January 22, 2014 11:45 PM
To: General discussion for Windows Installer XML toolset.
Hi,
I have three VB6 components in a VB6 project I want to install and register.
Two are ocx's and
Thanks for the reply. I set the value of WixMbaPrereqPackageId variable to
the id of dotnet 4.0 package included in my bundle. So it now runs well on a
Windows Xp PC where dotnet 4.0 is not installed. But it still doesn't run on
the Windows 7 PC where dotnet 4.0 is not installed. Log files of
insta
sys.BUILDARCH is the value of the -arch argument to candle, which Votive sets
to the Platform property of the project during build (so it will reflect the
build configuration, and if you build two MSIs with the same project will
probably be different values for each one). It has NOTHING to do wi
If they are not in DTF then the WiX toolset doesn’t provide them. It’s assumed
that most of what drove you to managed code would already be in the Framework
so there isn’t the same level of need to invent the wheel.
Having said that, I like John’s reply. Cool system. I’ll have to remember that
That directory does not exist on my Win8.1 box (where I have not yet installed
the ADK). So, that can’t be the runtime requirement, unless the API cannot be
used outside of generating ISOs/DVDs.
Blair
From: Phill Hogland
Sent: Thursday, January 23, 2014 6:45 AM
To: General
Windows Installer a long time ago swallowed the actual error code and
determined that this error message was the most likely cause of any failure to
install/start a service. With time that’s been proven wrong, but as Raymond
Chen would tell you about maintaining backward compatibility…
What yo
sys.BUILDARCH uses the value set via the MSBuild Platform property (x86 for
32-bit intel, etc.) automatically with recent releases of WiX. And most of the
time you don’t need to set the Win64 attribute because the same input (the
-arch argument to candle) that sets the BUILDARCH value from the M
InstallPrivileges will work, but is deprecated (or at least should have been).
InstallScope is preferred. There is no need to do both.
Blair
From: roberthyang
Sent: Wednesday, January 22, 2014 4:26 PM
To: General discussion for Windows Installer XML toolset.
Also look i
If you are using VS11 you should be able to use MSBuild on the SLN files
instead of devenv.exe (I haven’t noticed any non-MSBuild project types left in
VS 2012, but maybe there are some).
You could probably replace those two calls with something like:
call C:\Windows\Microsoft.NET\Framework\v
Are you including the .NET 4.0 framework package in your bundle and setting the
WixMbaPrereqPackageId like here?
http://blogs.msdn.com/b/heaths/archive/2011/10/28/introducing-managed-bootstrapper-applications.aspx
WixMbaPrereqPackageId lets the core managed bootstrapper know which package is
th
I made a managed bootstrapper using wix burn following instructions on the
book Wix 3.6: A Developer's Guide to Windows Installer XML(Chapter 16). I
used Prism 4.1 and targeted dotnet framework 4.0. It runs well on my Windows
7 PC where dotnet 4.0 and 4.5 are installed. But it doesn't run on anothe
"Permanent" would make it stay after an uninstall too, which is
probably not wanted.
--
Nicolás
2014/1/23 Jeremiahf :
>
>
>
>
> On Thu, Jan 23, 2014 at 9:47 AM, C B wrote:
>
>> During an installation or major upgrade, if a user has pinned the
>> application to their task bar, then after the i
Code was originally written sometime around 2001. It hasn't changed really
since then.
-Original Message-
From: Levi Wilson [mailto:l...@leviwilson.com]
Sent: Thursday, January 23, 2014 2:31 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SqlScript with large sc
I'm actually looking at it now :-) I can live with the initial, since
that's only going to happen the first time you run our installer and our
schema is not there. On an update (doing major upgrades) we are going to
have migration scripts run. Those should not be near what this initial one
is.
Loo
I assume most people live with the perf since no one has ever bothered to fix
the bug.
-Original Message-
From: Levi Wilson [mailto:l...@leviwilson.com]
Sent: Thursday, January 23, 2014 12:30 PM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] SqlScript with large s
What are other ways that people have gotten around it? It doesn't seem
desirable to execute `sqlcmd` from a CA.
On Thu, Jan 23, 2014 at 2:26 PM, Rob Mensching wrote:
> You'll want to think about security with that second option. I don't think
> the MSI property is the issue. I think it's the SQ
Classification: Public
Saw this, can't remember if someone mentioned.
This has been fixed in WIX 3.8
-Original Message-
From: J Rao [mailto:jr...@live.com]
Sent: December-26-12 2:59 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] No progress in msi progressbar when packed in bu
You'll want to think about security with that second option. I don't think the
MSI property is the issue. I think it's the SQLCA code itself that is slow
parsing. IIRC, there is a (very old) bug about the perf problem. Maybe you'd
like to tackle it?
-Original Message-
From: Levi Wilson
Sorry I didn't mention this before, but the database is already going to
exist. Our customers create this beforehand. The installer will just be
running the SQL script for the initial schema to create all of our tables,
triggers, sprocs, etc.
When looking at the installer log, I see two lines that
I am using a to create our database schema. I exported the
schema using RedGate. The file is 10MB (I know, I know...). Everything
works as expected, but during the installation the "Configuring SQL Server"
takes forever.
I know, 10MB file with 144k lines of SQL to parse is a lot...is there a
bett
Classification: Public
I do something similar:
In Product.wxs:
CA: Verify if this is
an upgrade...
WIX_UPGRADE_DETECTED
Then in my custom action DLL I have a method DisplayUpgradeMessage:
var result =
session.Message(
Install
I always do it in the Pre-build event command line. My example.
"$(WIX)bin\heat.exe" dir "$(ProjectDir)..\folder\files" -dr INSTALLLOCATION
-cg someGroup -gg -sf -srd -svb6 -var "var.somevar" -out
"$(ProjectDir)someGroup.wxs"
On Thu, Jan 23, 2014 at 1:38 AM, Graham Allwood wrote:
> Hi,
>
> I ha
You could use WIX_UPGRADE_DETECTED as a condition.
On Thu, Jan 23, 2014 at 11:57 AM, Brian Enderle wrote:
> Yes, I am using the WIXUI_InstallDir.
>
> Brian
>
> Brian
>
> If you can't explain it simply, you don't understand it well enough. -
> Albert Einstein
>
>
> On Thu, Jan 23, 2014 at 11:57
Yes, I am using the WIXUI_InstallDir.
Brian
Brian
If you can't explain it simply, you don't understand it well enough. -
Albert Einstein
On Thu, Jan 23, 2014 at 11:57 AM, Jeremiahf wrote:
> Are you using a UI?
>
>
> On Wed, Jan 22, 2014 at 10:56 AM, Brian Enderle wrote:
>
> > Is there a wa
On Thu, Jan 23, 2014 at 9:47 AM, C B wrote:
> During an installation or major upgrade, if a user has pinned the
> application to their task bar, then after the installation has completed,
> the taskbar shortcut is removed from "\AppData\Roaming\Microsoft\Internet
> Explorer\Quick Launch\User
Why not right click on the DB, tasks and generate in MS? What version of
SQL?
On Thu, Jan 23, 2014 at 10:52 AM, Levi Wilson wrote:
> I am using a to create our database schema. I exported the
> schema using RedGate. The file is 10MB (I know, I know...). Everything
> works as expected, but duri
Are you using a UI?
On Wed, Jan 22, 2014 at 10:56 AM, Brian Enderle wrote:
> Is there a way using 'MajorUpgrade' to prompt the user with a message
> (either in the installer window or via a pop-up window) that running this
> installer will remove previous versions of this product and let the us
I am using a to create our database schema. I exported the
schema using RedGate. The file is 10MB (I know, I know...). Everything
works as expected, but during the installation the "Configuring SQL Server"
takes forever.
I know, 10MB file with 144k lines of SQL to parse is a lot...is there a
bett
Classification: Public
I have fixed my file copy issue
I have a x86 MSI and a x64 MSI that installs 2 files that come in x86 and x64
flavours :)
I know use this condition to fix it:
32 bit:
NOT Msix64 OR $(var.Platform) = "x86"
64 bit:
Msix64 AND $(var.Platform) = "x64"
Steve
-Original Mess
During an installation or major upgrade, if a user has pinned the
application to their task bar, then after the installation has completed,
the taskbar shortcut is removed from "\AppData\Roaming\Microsoft\Internet
Explorer\Quick Launch\User Pinned\TaskBar". The shortcut remains inside the
taskbar,
I above been reading up on the dism api, and while I have not gotten very
far, one thing that confuses me is the requirement stated in the following
link of:
"The binary files for your customized solutions must be saved in the same
directory as the DISM binaries installed by the Windows ADK. For ex
The .NET Framework API's are entirely satisfactory except in terms of error
returns. We don't check for he existenece of a database in the custom action
code as we deploy to cloaked SQL servers (browsing disabled, servers operating
on non-standard, high number ports, no DNS to remote SQL server
Being out of the WiX installer world for a handful of years, I was used to
writing all of my custom actions in C++. Getting back into this I noticed
that it is now acceptable to write them in C# and the DTF.
That being said, I have a custom action that is currently written in C++
that checks for t
Pre-vista OS the name of the account for sid S-1-5-18 was "NT
AUTHORITY\SYSTEM"
http://support.microsoft.com/kb/163846
Post-XP/2003 (and possibly on XP/2003 with a SP level, I do not recall,) the
name of the same S-1-5-18 sid "\Local System"
http://support.microsoft.com/kb/243330
When working dir
36 matches
Mail list logo
