Thanks
Rob
--
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs
Great. That was my problem. Thanks for your help. Much appreciated
Rob
On 23 January 2013 11:48, Rob Hamflett wrote:
> Starting with Vista the WinSxS runtime assemblies aren't committed until
> InstallFinalize. This meant my service couldn't be started as part of
> the S
I think a log file would be necessary:
https://support.firegiant.com/entries/24024218-Create-a-log-file-
On Wed, Jun 26, 2013 at 11:23 AM, Steve Merckel wrote:
> I have an ExePackage defined,
> which can output a few different exit codes. What I would like to have
> happen, is to prompt for re
It is possible however you'd need to write a custom BA. The wixstdba
(provided with the WiX toolset) is designed to create a "single
installation experience" not "bunch of independent installs popping up".
On Thu, Jun 27, 2013 at 2:48 AM, Vinoth M wrote:
> I think this is not possible with WIX
Not today. Multi-MSI Transaction API was buggy (that's why you don't seen
major Microsoft products using it). We should eventually add it as an
opt-in feature to Burn at some point so that if your MSIs can handle it
Burn will support it.
On Thu, Jun 27, 2013 at 10:01 AM, Phil Wilson wrote:
> Th
That's reasonable too.
I've considered creating such a thing before but it's not particularly
interesting problem for me so it's not a place where I'd choose to invest
my volunteer time.
On Thu, Jun 27, 2013 at 10:25 AM, Alan Fors wrote:
> That's a reasonabl
ssage-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: Thursday, June 27, 2013 12:17 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-users] [SPAM] Re: Bootstrapper multiple MSI's don't rollback
> to a working installed state
&g
Bug http://sourceforge.net/p/wix/bugs/2766/ captures some of the relevant
issues. This is a very hard problem to solve correctly in Burn (think about
all the scenarios for a while and you'll see how deep the rabbit hole
goes). Multi-MSI Tx is a reasonable way out if it worked reliably (our
tests sh
MSIs created by WiX toolset will run fine (as long as you target Windows
Installer that supports Win2k).
However, any WiX code that gets carried with your MSI (like custom actions
or Burn) require WinXP SP2+.
On Thu, Jun 27, 2013 at 12:36 PM, Andrew Jones
wrote:
> Am I right in assuming that an
Over the next couple days, we're going to be doing some upgrades to the
http://wixtoolset.org infrastructure. As a result the website will probably be
up and down and all around. Apologies in advance for any issues this might
cause you.
---
Burn is only used when you create a Bundle. Any version of the WiX toolset
can target any version of the Windows Installer so I recommend using the
latest version, v3.7.
On Thu, Jun 27, 2013 at 1:23 PM, Andrew Jones wrote:
> > MSIs created by WiX toolset will run fine (as long as you target Wind
Wow, look, I'm self consistent system (at least in email). Not bad for a
human, eh?
On Thu, Jun 27, 2013 at 9:46 AM, Nick Ramirez wrote:
> I think you're right. This other thread seems to agree:
>
> http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Installl-upgrade-several-MSIs-in-
I sent email end of last week noting big infrastructure changes to website.
We're still working through those changes. It should be all good again
by end of day Monday.
On Sun, Jun 30, 2013 at 6:11 PM, Phill Hogland wrote:
> FYI - Tonight when I click on the button "Wix v3.7 released! Download>
I don't know what in Burn would lock existing files. Burn is very
self-contained and only uses files it carries with it, although a custom BA
can do anything. If you haven't already, I'd recommend using Process
Monitor to see if what locks your files when they are trying to be removed.
I'd be very
You're doing great!
It would be a reasonable thing to bug... but it's fixed in a more recent
build so no need to do that now.
On Tue, Jul 2, 2013 at 7:40 AM, Adam Roper wrote:
> So that's two responses saying that this is a known thing. Do I add that
> as a bug? Sorry, I'm new to this list,
Burn doesn't do things that the BA can do easily to avoid bloating the
engine (and the BA interface) with lots of stuff to maintain. In WiX v3.8
the wixstdba looks up the display name for the related bundle and displays
that.
On Tue, Jul 2, 2013 at 6:40 AM, Wesley Manning wrote:
> Happens to me
WixBA is written in managed code.
On Tue, Jul 2, 2013 at 1:53 AM, DavidH wrote:
> I'm aware the CA won't stop anyone who really wants to circumvent it, but
> hopefully it'll at least reduce the number of people who download packages
> they shouldn't.
>
> Thanks for the pointers about WixBA - I'
mp; Visible attribute of all the Package
> elements in the bundle to "yes".
> Thus when the bundle is finished it has an entry in the ARP but
> uninstalling it essentially does nothing.
>
> However, we both don't want this. Here is an entry from Rob Mensching's
>
gt; The bundle provided by burn supplies a cache external to Windows Installer
> for the MSI with its CABs (which will only be cleaned if the bundle's ARP
> is used instead of the MSIs, as pointed out by Rob).
>
> Burn promotes usability on many levels (not withstanding the occasion
I think the Shell caches aggressively. Try restarting and see if the Shell
still tells you it's signed.
On Mon, Jul 8, 2013 at 4:13 AM, David Watson wrote:
> It should come up as unsigned in the UAC prompt, if you have that disabled
> you won't see anything. You can usually still install it.
>
The Merge Modules have a bug in them. Have the produce fix them... or
ignore the warning.
On Wed, Jul 10, 2013 at 9:21 AM, Kathy Morey wrote:
> I am creating a WiX installer for an application that requires some
> Microsoft merge modules.
>
> I'm getting several warnings like:
>
> warning LGHT1
Steve, basically, yes:
http://robmensching.com/blog/posts/2008/10/10/what-are-.wixlibs-and-why-would-you-use-them
On Thu, Jul 11, 2013 at 5:48 AM, Steven Ogilvie wrote:
> Sigh,
>
> I am confused... When I was using InstallShield (for many years) I was
> told to always use Merge Modules, easier f
Since you're using a RemotePayload element, the
SuppressSignatureVerification isn't going to do anything. You will want to
remove the certificate information from the RemotePayload and populate the
Hash instead.
On Wed, Jul 10, 2013 at 11:58 PM, Tobias S wrote:
> At first glance I'd say to Supp
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> SuppressModularization="yes"/>
> SuppressModularization="yes"/>
> SuppressModularizati
The ARP size is the installed size, not the size of the Bundle. 415MB seems
with in range if the 120MB was all compressed stuff.
On Fri, Jul 12, 2013 at 8:16 AM, Niander Neves de Assis <
niander.ne...@gmail.com> wrote:
> Ok, But my bootstrapper (the .exe file generated) has the size of 120MB,
>
That looks like an extremely long path as well. Have you exceeded the 260
chars the NETFX supports?
On Thu, Jul 18, 2013 at 8:20 AM, Hoover, Jacob
wrote:
> Can you humor me and try building the project via the command line when
> using the "VS 2012 x86 Native Tools Command Prompt"?
>
> -Orig
re there?
Also, you didn't GAC the wix.dll did you (path looks a little like it might
be GAC'd)? That would definitely cause issues as well...
On Thu, Jul 18, 2013 at 9:26 AM, José Marques wrote:
> How can I check that?
>
> On Thu, Jul 18, 2013 at 5:17 PM, Rob Mensching
> wrot
Sure. Use Burn. The MSI will just be inside the executable. See the
"Bundle" element.
On Thu, Jul 18, 2013 at 11:30 AM, Steven Ogilvie
wrote:
> Classification: Public
> No I don't believe so...
>
> -Original Message-
> From: Mamidi, Balasubrahmanyam [mailto:balu.mam...@flightsafety.com]
dark.exe can extract the files. This error has been intermittent. If you
have a consistent repro, it would be awesome if you could use Process
Monitor to capture everything going on through the failure. Then put the
.pml file and the corresponding burn.log somewhere and I'd like to take a
look.
O
Always better to start with what you are trying to accomplish rather than
ask a very narrow question with no context.
On Mon, Jul 22, 2013 at 3:18 PM, Sean Farrow
wrote:
> Hi,
> I'm just in the process of writing a custom action, I know file version
> functions are in fileutil.cpp/h. Are Product
The cool thing is that if you always use Bundles to install your MSI
packages, shared MSI packages will be correctly reference counted and only
removed when the last Bundle that needs it is removed. Totally avoids all
the bad behaviors.
On Tue, Jul 23, 2013 at 10:00 AM, Wesley Manning wrote:
> I
nderstand correctly this is
> not possible with burn, which is a shame because it has everything we need
> and does it very well. What is a good alternative for this? dotNetInstaller?
>
> Regards
> Tomas
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robme
Can you provide more details about how you are executing elevation?
On Wed, Jul 24, 2013 at 8:25 AM, Hoover, Jacob
wrote:
> Wix/Burn doesn't have a service portion written so it's dependent on
> Windows Installer constraints. If there is a need to update without admin
> privileges, either an Adm
ing such a system.
We don't provide something like that in WiX toolset today.
On Wed, Jul 24, 2013 at 10:22 AM, Rob Mensching wrote:
> Can you provide more details about how you are executing elevation?
>
>
> On Wed, Jul 24, 2013 at 8:25 AM, Hoover, Jacob > wrote:
>
>>
MSP didn't fail because Burn recognized it wasn't to be installed:
Planned package: cs201022_HotFix00,
state: Absent, default requested: Present, ba requested: Present, execute:
None, rollback: None, cache: No, uncache: No, dependency: None
On Wed, Jul 24, 2013 at 3:24 AM, rowbot wrote:
> Hi
Hmm, well, certainly seems to be something going wrong but can't tell what
exactly based on the log files. Would be a great idea to open a bug with as
many details about the issue as possible.
On Wed, Jul 24, 2013 at 5:06 AM, TimM wrote:
> Sorry about that
>
> Try this link: https://www.dro
And what version of WiX v3.8?
On Thu, Jul 25, 2013 at 6:59 AM, David Watson wrote:
> What error?
>
> -Original Message-
> From: Pasquale Fersini [mailto:basquale.fers...@gmail.com]
> Sent: 25 July 2013 14:42
> To: General discussion for Windows Installer XML toolset.
> Subject: [WiX-use
a single .msi).
>
> / Tomas
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: den 24 juli 2013 19:20
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] [wix-users] Impact of installed burn?
>
>
Slight amendment: "You should NOT call any custom actions **that modify
machine state Before InstallInitialize or** After InstallFinalize "
On Thu, Jul 25, 2013 at 6:08 AM, Steven Ogilvie wrote:
> Classification: Public
> You should NOT call any custom actions After InstallFinalize.
>
> -Ori
It's ARP being magical. Never quite tracked down how they did it.
Fortunately, Burn is smart enough to recognize that it is already elevated
and doesn't ask again.
On Thu, Jul 25, 2013 at 3:55 AM, Tobias S wrote:
> Any idea on that behavior? Feedback highly appreciated.
>
> Best regards,
> To
gt; Subject: Re: [WiX-users] VS 2013 support
>
> Anyone?
>
>
> On Jul 17, 2013, at 9:50, "Ivanoff, Alex"
> wrote:
>
> > Rob,
> >
> > Do you plan VS 2013 support?
> >
> >
> > On Jul 16, 2013, at 9:08, "Ivanoff, Alex"
&g
Get a BA that recognizes that as a failure condition? Or, if you are using
wixstdba, help us extend wixstdba to treat that as a failure condition. The
Burn engine is doing as it is told.
On Thu, Jul 25, 2013 at 1:25 AM, rowbot wrote:
> Okay, but given the scenario when a bundle contains only on
Hmm, where did you get that build from? There is no WiX v3.8.5506 build.
On Thu, Jul 25, 2013 at 9:15 AM, Pasquale Fersini <
basquale.fers...@gmail.com> wrote:
> Application error
>
> Wix 3.8.5506.0
>
>
> 2013/7/25 Rob Mensching
>
> > And what version of WiX
Arg! I thought that bug was fixed to give a better error message. Jacob, if
you're still interested, that's the bug to fix. To implement a better error
message in the log that I thought was already there. Interested?
On Thu, Jul 25, 2013 at 10:17 AM, TimM wrote:
> Okay we think we have this f
Addons (and patch) bundles follow the main bundle (more written here:
https://support.firegiant.com/entries/24024208-Bundle-chain-execution-order-).
To get the behavior you want, you'd need an upgrade relationship.
I think a custom BA could override the default behaviors without using an
upgrade r
Did you also add a reference to the extension?
On Thu, Jul 25, 2013 at 2:04 PM, Drake, David wrote:
> I'm working on creating a new installer for a self-hosted web service and
> there are a couple of things I'm hoping there's an easier way to handle.
> For this thread, I'm interested in the MSM
I think there were a couple bugs opened on that fixed in v3.8.
On Thu, Jul 25, 2013 at 2:25 PM, Drake, David wrote:
> I think I've already found out what was wrong. I created my WIX Resource
> directory via the wix3.7-binaries.zip download, not by copying from the
> Program Files installed dire
Am I abusing the addon feature?
>
> Wes
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: July 25, 2013 5:46 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn Addons - reevalulate and uninstall
There were issues a while ago with Windows XP builds. I believe they were
all fixed. Maybe that build is old enough to have the issue. Try a later
build and see if that helps.
On Fri, Jul 26, 2013 at 12:18 AM, Pasquale Fersini <
basquale.fers...@gmail.com> wrote:
> Sorry Rob,
> but
; no problems.
>
> Wes
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: July-26-13 1:03 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn Addons - reevalulate and uninstall addon
> bundle on
Cool. Two things:
1. Let's start the assignment agreement process (
http://wixtoolset.org/about/assignment-agreement/).
2. Let's have this conversation on wix-devs. That's more appropriate.
On Mon, Jul 29, 2013 at 5:38 AM, wrote:
> Hello,
>
> I have been tasked with discovering if I c
Look in the Bundle's log file. It'll show what was installed. If anything
per-machine was installed, it will have to elevate.
On Tue, Jul 30, 2013 at 1:14 AM, David Watson wrote:
> I don't think burn currently supports this kind of scenario well (it may
> but
> I am not an expert).
>
> What you
It can be UI-less if your BA doesn't show UI.
On Tue, Jul 30, 2013 at 8:00 AM, Tom - wrote:
> Good afternoon,
>
> >From my previous problems, I pieced together a bootstrapper that should
> do nothing but uninstall a non-WiX installation of a program. I don't need
> the bootstrapper UI. I wouldn
Should be back now. AppPool was dead, I'll ask why.
On Tue, Jul 30, 2013 at 8:42 AM, Alain Forget wrote:
> +1
>
> -Original Message-
> From: Tony [mailto:yellowjacketl...@gmail.com]
> Sent: Tuesday, July 30, 2013 11:36
> To: WiX Users
> Subject: [WiX-users] wixtoolset.org down?
>
> I ge
I like that way.
On Fri, Aug 2, 2013 at 12:51 PM, Tony White wrote:
> I don't really understand your suggestion.
> I have 18 tabs of google searches open, and reading the WiX help, and
> looking at the source code for four days now.
> Finally found this:
> http://stackoverflow.com/questions/169
Note: that can confuse Burn because it is designed to not run the BA
elevated.
On Sat, Aug 3, 2013 at 9:36 AM, Phill Hogland wrote:
> The implication that I take from your questions is that you are trying to
> write something to the Program Files area from the bootstrapper. Generally
> I think
Change the 4th field of the version.
On Tue, Aug 6, 2013 at 5:00 PM, Blair Murri wrote:
> Patching becomes more difficult whenever you change the ProductVersion.
>
> > From: chr...@iswix.com
> > To: wix-users@lists.sourceforge.net; wix-users@lists.sourceforge.net
> > Date: Tue, 6 Aug 2013 14:01
Even better would be to get the MSI fixed. Sounds like there are a couple
issues there. Everything should "Just Work" without forcing anything.
On Wed, Aug 7, 2013 at 2:10 AM, Hendryk Irmischer wrote:
> Yep, ForcePerMachine="yes" did the trick.
>
> First I tried to copy the missing CustomActions
You need to format the string.
On Thu, Aug 8, 2013 at 6:18 AM, Veli-Matti Visuri <
veli-matti.vis...@futuremark.com> wrote:
> Hi, I've been working on a bootstrapper with a customized UI and I cannot
> figure out a way on how to "translate" the burn built-in variables from the
> engine to the UI
Sounds like the machine's root certificates are out of date. Burn's call to
verify the payloads will cause Windows to update the root certificates
automatically, if connected.
On Thu, Aug 8, 2013 at 6:41 AM, Adkins, Christopher <
christopher.adk...@docuware.com> wrote:
> Hi everybody!
>
> I was
Not easily supported. The Windows Logo says to not create uninstall
shortcuts so it's not an easily supported scenario in Burn.
On Thu, Aug 8, 2013 at 5:14 AM, Marc Bartsch wrote:
> Hi,
>
> We create an installation .exe with burn that successfully installs .NET4
> as a prerequisite and our .msi
Why not put D2.dll in it's own Component?
On Sun, Aug 11, 2013 at 10:37 PM, Michael Partridge <
michael.partri...@petrosys.com.au> wrote:
> Hi All,
>
> I was wondering if the state of play has changed at all since
> http://stackoverflow.com/questions/703359/wix-add-new-file-to-shared-componentwa
Yes, the Component Directory attribute is a reference to the Directory with
matching Id. This pattern is used heavily in the WiX toolset. The Directory
attribute isn't required when the Component element is nested under a
Directory. The doc could be updated to note that a Component's Directory
refe
Burn will automatically detect if MSIs are installed. No need to do
anything. Additional help probably requires more detail about what exactly
the searches and conditions were.
On Mon, Aug 12, 2013 at 12:36 PM, Marlos Gottschild <
marlos.gottsch...@gmail.com> wrote:
> Hello,
>
> My name is Marlo
roduct1 - it's already in the field and won't have
> any updates. In reality Product1 and Product2 are different versions of our
> product that can be installed side-by-side - users like to have access to
> previous versions.
> >
> > Cheers,
> > Michael
> >
>
PS: The code you are interested in is in
src\ext\BalExtension\wixstdba\WixStandardBootstrapperApplication.cpp,
LoadLocalization(). That uses the helper function LocProbeForFile() that is
in src\dutil\locutil.cpp
On Tue, Aug 13, 2013 at 7:17 AM, TimM wrote:
> So Phill, did you have a chance to t
"[ServicePackLevel]"?
On Tue, Aug 13, 2013 at 9:57 AM, Christopher M. Bunn <
cmb...@torchmarkcorp.com> wrote:
> Is there a way to display the actual value of ServicePack embedded in the
> message in Burn? Thanks!
>
>
>
> (VersionNT >= v5.1 AND ServicePackLevel >= 3) OR (VersionNT64 >= v5.1
> AN
If you don't reference anything in a Fragment it isn't included in the
final MSI. That's one of the most powerful features of the WiX toolset.
On Fri, Aug 16, 2013 at 8:17 AM, TimM wrote:
> Quick questions about components within a referenced wixlib.
>
> If you add a new component to a WiX inst
Yes. Remember the WiX toolset model is based on C/C++ concepts. In C/C++
you document the functions people can call in your .lib files.
On Fri, Aug 16, 2013 at 8:43 AM, TimM wrote:
> Okay that makes sence
>
> So do you then just document what components and/or CompoentGroups are in
> your wixli
I agree. That would be a pretty cool feature. VC++ doesn't provide it but
it'd be cool for .lib files as well.
On Fri, Aug 16, 2013 at 8:50 AM, TimM wrote:
> Yes Rob that is true with added fragments, but with the fragments as long
> as
> they are part of your proj
Be very, very careful using ADDLOCAL and friends directly on the
command-line. You can really get confused behavior in the MSI if you get
that wrong. You'll want to test lots and lots of scenarios (install,
uninstall, patch, repair upgrade) with all the different permutations.
On Mon, Aug 19, 201
You want DetectCondition. InstallCondition says whether a package should
be installed on the machine. If false and the package is installed, it will
uninstall the package.
On Mon, Aug 19, 2013 at 7:21 AM, Kenneth Porter wrote:
> --On Monday, August 19, 2013 8:01 AM -0700 Phill Hogland
> wrote:
WiX toolset install does.
On Mon, Aug 19, 2013 at 11:26 AM, yugolancer wrote:
> Hi Guys,
>
> Would you show me an example of bootstrapper which simply checks on start
> if
> .NET 4.0 is installed and install if not and THEN just start my regular
> setup AS IS without installing it in background
Just like everything else: dark.exe.
On Mon, Aug 19, 2013 at 11:44 AM, jo...@msli.com wrote:
> Is there a way to disassemble a bundle?
>
>
>
> NOTICE: This email may contain confidential information. Please see
> http://www.meyersound.com/confidential/ for our complete policy.
>
>
> --
An entire Fragment is included when referenced.
On Mon, Aug 19, 2013 at 12:15 PM, Marlos Gottschild <
marlos.gottsch...@gmail.com> wrote:
> Hi,
>
> I have a wixlib with Components, ComponentGroups and Features and another
> wix project referencing this library. And I need to selectively choose
>
Don't have to be in separate files.
On Mon, Aug 19, 2013 at 12:44 PM, Marlos Gottschild <
marlos.gottsch...@gmail.com> wrote:
> Works like a charm. Thanks Rob and Philippe.
>
> For future reference, I moved both ComponentGroup and Feature to a separate
> file,
Did you sign the bundle according to the documentation on the Insignia page?
On Mon, Aug 19, 2013 at 4:57 PM, jo...@msli.com wrote:
> I sign the bundle I get this error.
> An unsigned bundle seems to work.
>
> On Mon, 2013-08-19 at 15:36 -0700, jo...@msli.com wrote:
> > Looks like my log file w
tracker,
please contact me so we can sort out any problems. As noted above, a lot of
this is new technology so please be patient as we work out a few kinks and add
more functionality.
In the meantime, keep coding. You know I am!
virtually,
Rob Mensching
Your Friendly Neighborhood
Online documentation should be back again. There is also always the wix.chm
that is installed with the WiX toolset.
On Wed, Aug 21, 2013 at 8:15 AM, Steven Ogilvie wrote:
> Is this for Burn, wouldn't you use Payload
> i.e.
>
> Steve
>
> -Original Message-
> From: Phyx [mailto:loneti...@
me: path1
> > > > >
> > > > > Exception Type: System.ArgumentNullException
> > > > >
> > > > > Stack Trace:
> > > > >at System.IO.Path.Combine(String path1, String path2)
> > > > >at
> Microsoft.Tools.WindowsInstallerXml.Unbinder.UnbindBundl
Bob wrote a nice blog entry about this:
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
Lots of tradeoffs to consider.
On Wed, Aug 21, 2013 at 1:33 PM, wrote:
> Thank you for the information, Phil. This raises another bunch of
> questions:
>
> Why is the default in this location in t
t display properly
> in IE8?
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 21 August 2013 08:25
> To: wix-users@lists.sourceforge.net
> Subject: [WiX-users] New Bug and Feature Request location:
> http://wixtoolset.org/issues/
Fixed. Somehow the search results page lost it's HTML5 doctype causing the
older browsers to go into quirks mode. I fixed the doctype and it should be
rendering better in IE7+.
Thanks for the heads up.
On Wed, Aug 21, 2013 at 2:30 PM, Rob Mensching wrote:
> I didn't know it look
go to the site no bugs are shown, you
> have to click Untriaged to see any thing?
>
> Neil
> ____
> From: Rob Mensching [r...@robmensching.com]
> Sent: 21 August 2013 23:09
> To: General discussion for Windows Installer XML toolset.
> Sub
With Burn that is not the approach I would take. A bit of my opinion here:
http://robmensching.com/blog/posts/2012/6/25/b-is-for-bundle-and-thats-good-enough-for-me
You are, of course, entitled to your own opinion of the best approach.
On Thu, Aug 22, 2013 at 12:40 AM, Phyx wrote:
> Hi Steve,
, am
> I missing something?
>
> Also, I created my account without an alias so not my email address is
> display - can I edit my account?
>
> Neil
>
> -----Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 21 August 2013 08:25
> To:
Yeah, the error cases around accounts that are not yet verified are not
great. Another area to improve.
On Thu, Aug 22, 2013 at 1:29 PM, Neil Sleightholm wrote:
> Did you get the activation email? (Mine went to the Junkmail.)
>
> -Original Message-
> From: Phill Hogland [mailto:phogl...@
Ahh, yes. That may be a bug.
On Thu, Aug 22, 2013 at 12:28 PM, Neil Sleightholm wrote:
> Ah, in that case it needs to "know" that when I click "My Open" I need to
> logon.
>
> Neil
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robme
Might be related to: http://wixtoolset.org/issues/3643/
On Fri, Aug 23, 2013 at 3:24 AM, Bruce Cran wrote:
> I seem to have managed to get Burn rather confused. I have an MSI
> package with new product and upgrade codes in version 2.0 due to
> different builds being produced. I ask Windows Inst
Neil and Phill,
I believe I've added enough to address both of these issues. Go to:
http://wixtoolset.org/issues/edit/me
There you should be able to update your username (and full name and email*)
as well as re-send the activation email. I've also fixed the DNS records.
The wixtoolset.org was mis
It'd be great if you could contribute what you learned or maybe go in and
understand how the documentation is created for the WiX toolset to help
enhance it. The guys on wix-devs mailing list are very supportive of people
wanting to help improve.
Feature suggestions here are welcome but I always l
There's an issue open requesting WiX to write the AssemblySearchPaths in
64-bit hive. That isn't done today.
On Tue, Aug 27, 2013 at 12:27 PM, Edwin Castro <0ptikgh...@gmx.us> wrote:
> MSBuild uses the AssemblySearchPaths property to determine the locations
> where it searches for assembly refer
Often this on test VM machines but I suppose unmanaged machines not
connected to the internet would hit it.
Basically, you need to be connected to the internet occasionally to
participate in security since security changes over time (that which was
safe may become unsafe). Or so those that designe
I'm curious what happens when SourceDir is blank.
On Mon, Sep 2, 2013 at 10:25 AM, Phil Wilson wrote:
> My dumb search works just fine - I can't see what the issue is. This works
> for me:
>
> Sample.msi and thing.txt in the same directory.
>
>
> Depth="0">
>
Yes. You need a custom BA.
On Wed, Sep 4, 2013 at 3:49 AM, ak m wrote:
> Dear All,
>
> Launching Bootstrapper executable should only show the internal MSI
> interface.
>
> Not to show any of the Bootstrapper UI.
>
> Is this Possible?
>
> Any one please help me on this?
>
>
> Thanks in Advance.
Ship the patch in a Bundle.
On Wed, Sep 4, 2013 at 10:04 AM, George Fleming wrote:
> I have two applications, a MSI and a bootstrapper/UI that invokes the MSI.
> To prevent double ARP entries, we set the ARPSYSTEMCOMPONENT property in
> the bootstrapper .
>
> This works fine, except when we app
Manual is expected to be working now so if you find dead links, please do
file bugs about them.
On Wed, Sep 4, 2013 at 11:08 AM, Phill Hogland wrote:
> Sorry for the delay in responding to the last post. I updated my user info
> using the link provided in the email, however it always failed un
There are bugs open that track progress of 2013 support.
On Wed, Sep 4, 2013 at 11:16 AM, John H Bergman (XPedient) <
john.berg...@xpdnt.com> wrote:
> I noticed while looking through the history that there were checkins
> related to VS2013 Preview, including a branch merge. Does this mean that
My memory says SourceDir is blank until Source Resolution is executed.
On Wed, Sep 4, 2013 at 10:13 AM, Phil Wilson wrote:
> It will work only during first install, as Rob most likely knows. During
> repair, feature change, and uninstall the SourceDir location is (IIRC) the
>
uld be nice not to have
> to keep the old bundle around for the uninstall.
>
> Thanks for any info !
> -Rob
>
>
> --
> Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more!
> Disc
1 - 100 of 6083 matches
Mail list logo
