Re: [WiX-users] cannot open Wix tutorials on tramontana.co.hu

It was fixed yesterday. On Fri, Oct 5, 2012 at 5:41 PM, Bruce Cran wrote: > On 04/10/2012 20:31, akonsu wrote: > > http://wix.tramontana.co.hu/tutorial takes me to a viagra site or > something > > similar. has the server been hijacked? > > Strange, I just tried it and it has the old contents - t

Re: [WiX-users] cannot open Wix tutorials on tramontana.co.hu

On 04/10/2012 20:31, akonsu wrote: > http://wix.tramontana.co.hu/tutorial takes me to a viagra site or something > similar. has the server been hijacked? Strange, I just tried it and it has the old contents - though I definitely remember seeing it with the spammy content in the past. -- Bruce C

Re: [WiX-users] MsiPackage without upgrade

Not today. Who does that? On Fri, Oct 5, 2012 at 2:57 PM, Neil Sleightholm wrote: > I have a third party MSI that doesn't support upgrades, it expects the > user to uninstall the old version before installing the new one. Does the > burn engines MsiPackage element handle this? > > Neil > > Neil

Re: [WiX-users] candle failing from MSbuild w/ "The file exists"

After quite a bit of google'ing, I came across someone who had a similar issue which was fixed by emptying their %TEMP% folder. So, being desperate, I did just that and my builds started working again. It would seem there might be some sort of name collision somewhere, but I have no idea where (ca

[WiX-users] MsiPackage without upgrade

I have a third party MSI that doesn't support upgrades, it expects the user to uninstall the old version before installing the new one. Does the burn engines MsiPackage element handle this? Neil Neil Sleightholm X2 Systems Limited n...@x2systems.com -

Re: [WiX-users] rollback vital vs. package vital

Almost. The MSI package will be rolled-back (uninstalled if necessary) in the first case. In the second case, if the MSI did not rollback, the bundle install will continue with it on the machine (but failed). On Fri, Oct 5, 2012 at 11:46 AM, Nick Ramirez wrote: > Is the following bundle: > > >

Re: [WiX-users] Burn and MultiInstance installs

Burn doesn't support multi-instance MSI packages today. The way it tracks whether the MSI is already installed isn't designed to support multi-instance MSIs. It's a thing to implement in a future release. On Fri, Oct 5, 2012 at 1:30 PM, wrote: > Hello everyone, > > We currently have a c

[WiX-users] candle failing from MSbuild w/ "The file exists"

When attempting to build a wixproj from VisualStudio 2012/MSBuild, it started failing today with the below message. Can you provide any insight as to why this might be failing and what file it is complaining already exists? Note: If I run the candle command directly in the console, instead of thr

Re: [WiX-users] condition not working :(

Crap friggin nabble does that __ Steven Ogilvie Sent from my BlackBerry... 3 - 45 Bertrand Street Ottawa, ON Canada K1M 1Y5 Mobile: +1 613 299-2121 E-mail: sogil...@msn.com -Original Message- From: "Hoover Jacob [via Windows Installer XML (WiX) toolset]" Date: Fr

Re: [WiX-users] condition not working :(

I assume your condition must have been mangled/stripped when you posted. -Original Message- From: StevenOgilvie [mailto:sogil...@msn.com] Sent: Friday, October 05, 2012 3:24 PM To: wix-users@lists.sourceforge.net Subject: [WiX-users] condition not working :( Hi all frustrated... I have

[WiX-users] Burn and MultiInstance installs

Hello everyone, We currently have a custom boot strapper that collects the instance from the user and then we have a custom action in the install that will transform the Product and upgrade code for the install based on that instance. We are getting ready to convert another of our produ

[WiX-users] condition not working :(

Hi all frustrated... I have 3 files that are installed conditionally: I have a custom action to a dll that runs and sets the property as per log file: MSI (c) (4C!E4) [16:17:47:570]: PROPERTY CHANGE: Adding MYCORP_FOUNDPRODUCTPLATFORM property. Its value is 'x86'. MSI (c) (4C!E4) [16:1

Re: [WiX-users] Component/@Guid error

Not sure what the problem actually was. I scrapped what I had, and started over. Everything working now as expected. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Component-Guid-error-tp7579390p7581179.html Sent from the wix-users mailing list a

Re: [WiX-users] DIFxApp and upgrades

Hey James, Did you ever get any resolution to your problem regarding scanning for new hardware when your installation must first uninstall an older version? I'm in the same boat, and was curious if you made any progress since your last post. If you are continuing with your workaround, I'd really

Re: [WiX-users] WiX-users Digest, Vol 77, Issue 35

The machine is clean. In the install logs I can see all the existing dlls being removed and re-installed but there is no trace for the new dlls in the logs. Yes. Each dll is in its own component. Also, new dlls are also in new components. However the new components are part of existing componentg

Re: [WiX-users] I have heard that MSI is too complicated from a programmer's prospective

On 05/10/2012 17:23, Katherine Moss wrote: > Oh really? Nasty; I mean, why not just use a standard UI for that anyway > rather than that very complicated and non user friendly interface? I'm not > talking about accessibility here; some sighted individuals struggle with it > as well. Maybe we

Re: [WiX-users] I have heard that MSI is too complicated from a programmer's prospective

Oh really? Nasty; I mean, why not just use a standard UI for that anyway rather than that very complicated and non user friendly interface? I'm not talking about accessibility here; some sighted individuals struggle with it as well. Maybe we should talk to them about that? I tried over on th

Re: [WiX-users] I have heard that MSI is too complicated from a programmer's prospective

He's just installing the product itself and I think that it downloads .net if not already installed. I talked to him about it last night, and he said that because it was crunch time and beta time, he simply wanted a quick solution with less of a learning curve in order to get the product out in

Re: [WiX-users] FW: Issue using vsixpackage feature in wix 3.7.1001.0

Picture didn't come through but I think the MSI verbose log file is going to have more information. Particularly the error message that should show up near the string "value 3" in the log file. On Thu, Oct 4, 2012 at 10:05 PM, ezien Integral Solutions < ezie...@hotmail.com> wrote: > > > > > > > H

Re: [WiX-users] Creating localizable setups

That is the minimal set of steps. Maybe one day someone will contribute the work to wrap it up in the wix.targets so others would never have to see it. However, I'm not sure language transforms are the best way to distribute localized software any longer. With Burn, I think I would wrap up the "ne

Re: [WiX-users] In place upgrade issue in wix proj

Also, Is each DLL in its own component? For the new DLL are they in new components? -Original Message- From: Peter Shirtcliffe [mailto:pshirtcli...@sdl.com] Sent: Friday, October 05, 2012 8:49 AM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] In place

Re: [WiX-users] In place upgrade issue in wix proj

Make sure you're on a clean machine, apart from the previous version, and generate a verbose installation log. -Original Message- From: abhijit chakraborty [mailto:abhi.chak.ju...@gmail.com] Sent: 05 October 2012 14:42 To: wix-users@lists.sourceforge.net Subject: [WiX-users] In place upgr

Re: [WiX-users] Question about Properties and Custom Actions

Yep, as you say, the well-known directories wouldn't necessarily be used in an MSI and so wouldn't have a corresponding directory Id, which is a requirement of the function. -Original Message- From: Peter Hull [mailto:peterhul...@hotmail.com] Sent: 05 October 2012 13:31 To: WiX Users Subj

Re: [WiX-users] Question about Properties and Custom Actions

Thanks for the replies. > You can use MsiSetTargetPath() in your custom action to update an existing > directory Id. That would more closely model your intent and requires less > code. Good point, that's another option. I have been looking at what was done in the WixQueryOsDirs custom action - t

[WiX-users] Creating localizable setups

I was trying to create a localized setup in Wix. Lets say I support 20 languages. So, objective is to produce all the 20 mst's. Using InstallShield in one build I can create the msi and the and all the 20 transform files. Now I want to achieve this process using WIX. What I have figured out so f

Re: [WiX-users] DLL helper functions

It's the wide/narrow string thing again. LPWSTR (note the W) means wide string. You likely want LPSTR (or just char *, which is the same thing). -Original Message- From: Natalie Carr [mailto:natalie.c...@measuresoft.com] Sent: 05 October 2012 10:36 To: wix-users@lists.sourceforge.net Subj

Re: [WiX-users] patching issue: adding new file works but this throws out old files Sequence numbers in msi

Did you rebuild any of the files when you created the second MSI ? If so, then they will be different and will potentially be pulled into the patch. I assume you mean file sequence numbers, rather than component. Its normal for patched files to get new file sequence numbers. -Original Message

[WiX-users] DLL helper functions

Hi I am trying to write a helper function for my DLL so that I can call it from another function like in Wcautil. However it says error C3861: 'AppendCapEntry': identifier not found This is how I declare my helper function: static HRESULT AppendCapEntry(__in LPWSTR lpszString) And call it

[WiX-users] WixUI_FeatureTree problem

Hi, I bought a book: Wix: A developer's guide to windows installer xml and this is first time dealing with WIX, so I'm beginner at the moment, but I would like to change that :) On page 108 there is following line: If I include this line and build the project(I have visual studio 2010) i get