See
http://damianblog.com/2008/02/21/configuring-http-namespace-reservations-on-vista-using-wix/
All of the custom actions in that post are important. Note where they are
scheduled to execute.
--
Edwin
On Fri, May 10, 2013 at 7:36 AM, Brownfield, Cory wrote:
> To illustrate a problem I'm havin
1. Personally, I think moving all of the UI from the MSI to the Bundle is
going to be the best option going forward. MSI UI is not advancing and if
you're in Bundle it's better to have a seamless user experience that Burn
can offer. This is obviously just my opinion.
2. I do think Burn should corr
candle.exe has a lot of dependencies too. Did you add all of them?
On Fri, May 10, 2013 at 7:35 AM, Gary Larsen wrote:
> Hi,
>
>
>
> I'm new to VS 2010 and WiX so probably something is not configured
> correctly. Here's the build error:
>
>
>
> Error 1 The extension
> 'C:\a-r
Yes but you're .wxl and build language needs to be marked "neutral"... and
you won't be able to correctly build multiple languages of your MSI. I
think I recently made these tweaks to the WiX build process when I fixed
all the WixDistribution.wxl stuff. You might look at that.
On Fri, May 10, 201
Not sure I've ever been able to get a Windows subsystem app to connect back
to the console that launched it. It'd be cool if you figured out how to do
that.
On Fri, May 10, 2013 at 12:11 PM, Nick Miller wrote:
> Hi All,
>
> I was wondering if there was a way to output text to the console (like
>
Make sure the file version # is updated in file version under assembly info
within assembly info if you are using VS 2010 and above. Also, use Orca to
view the properties of an MSI installer.
J
On Fri, May 10, 2013 at 8:55 PM, Candy Chiu wrote:
> Hi,
>
> I ran into an issue that one of dll's i
Hi,
I ran into an issue that one of dll's in an upgrade wasn't copied to the
destination folder. I examined the msi with LessMSI, the files were
packaged correctly. I reviewed the File Versioning Rules at
http://msdn.microsoft.com/en-us/library/aa368599(VS.85).aspx. They didn't
solve my problem
Hi All,
I need to install .Net3.5 SP1 as a prerequiste if not met using Wix. I have
written code using Wix Burn.
My plan is to include dotNetFx35setup.exe - to be a part of the package(in
package) and i have specified it in ExePackage:SourceFile.
If .net 3.5 is not installed, i execute dotN
Awesome, thanks!
-Original Message-
From: Marco Tognacci [mailto:mark...@live.it]
Sent: Friday, May 10, 2013 5:31 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Help Menu for Custom MBA
Yes, because with Burn the standard command line args are parse
Yes, because with Burn the standard command line args are parsed by the engine,
and you'll find in your BootstrapperApplication.Command.Action the launch
action equal to Help (or Install, Uninstall, Modify, Repair...), and in
BootstrapperApplication.Command.Display the state of UI that is reques
Hi All,
Is there anything special I need to do to create a command line help menu in my
custom managed bootstrapper application?
Bootstrapper.Command.GetCommandLineArgs() seems to ignore /?, /h, and /help
completely...
Thanks,
Nick
Nicholas Miller (Network Administrator)
LiveTechnology Holdi
Ok, I missed that. You mean the run of netsh.exe? That's not what is usually
referred to as a script (as in vbscript etc). Your INSTALLFOLDER won't
exist by the time you run that custom action because it's after
RemoveFolders. I don't think that should make a difference, but it's
possible that Win
The script included in my email doesn't work on Windows 7. It's pretty simple
(no environment variables, etc.). It produces an MSI that can be installed but
not uninstalled.
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: Friday, May 10, 2013 10:22 AM
To: 'Gen
Based on the documentataion looks like this is the clsid of the com class
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Registering-ComPlus-and-Assigning-a-User-tp7585575p7585793.html
Sent from the wix-users mailing list archive at Nabble.com.
Hi All,
I was wondering if there was a way to output text to the console (like error
messages) when running a BA in silent mode? If not, is there some other way I
can alert a user to an error without loading the UI?
Thanks,
Nick
-
Classification: Public
Actually this turned out to work for me:
WIX_UPGRADE_DETECTED AND SERVER_INSTALL="0"
-Original Message-
From: Steven Ogilvie [mailto:steven.ogil...@titus.com]
Sent: May-10-13 12:51 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
Classification: Public
Thanks very much Phil
I will do a:
OLDERVERSIONBEINGUPGRADED OR UPGRADINGPRODUCTCODE
AND SERVER_INSTALL="0" >
Thanks,
Steve
-Original Message-
From: Phil Wilson [mailto:phil.wil...@mvps.org]
Sent: May-10-13 10:25 AM
To: 'General discussion for Windows Installer
Ack, NT 4.0 is a bit dead these days. Odds are it's an issue with the engine
itself using newer API's. If you don't need all of the new features within
Wix, you "could" use an older branch. If you need the newer features on the
older OS, you'd have to back port all the non-compatible API's. I
Hi,
Is there any way to change the output directory of an MSI?
I have it building to my custom folder, however its builds like so :
CustomFolder\en-US\Setup.msi
I would like it to build to : CustomFolder\Setup.msi
Is this possible?
Thanks
Natalie
--
It's more likely related to something that is no longer correct during the
uninstall. Between DeleteServices and InstallFinalize the items that are
uninstalled include registry entries, type libraries, environment variables,
files, and folders.
Deferred and before InstallFinalize basically means
To illustrate a problem I'm having with a real project, I created a test script
that runs a custom action that requires elevated privileges during uninstalls.
If I configure it to run before "InstallFinalize" (deferred, no impersonation),
the uninstall fails to complete. The event log says "A
Hi,
I'm new to VS 2010 and WiX so probably something is not configured
correctly. Here's the build error:
Error 1 The extension
'C:\a-release\Setup\Setup\WixSystemToolsExtension' could not be loaded
because of the following reason: Could not load file or assembly
'file://
Major upgrades have a property that gets set when the older version is
found. To use Bob's example:
OLDERVERSIONBEINGUPGRADED can be used as your condition.
If you're referring to an installed product that is being uninstalled and
upgrades, use UPGRADINGPRODUCTCODE as the cond
Hello WiX users,
we generated with WiX 3.7 a bootstrapper exe, and tried it on XP, Win7 and
it works fine. But on an NT (4.0) machine we get "... is not a valid NT
application" error when starting the exe. Is thre a previous version of WiX
that supports WinNT, or do we have to write an own bootstr
24 matches
Mail list logo
