Re: [WiX-users] What should i sign (digitaly)?

Thank you for your answers @Rob, @Stephen and @John @Rob I don't understand either why i would sign files that are not ours, hence the question, so i know how the things are done. So I guess there is no written rule about signing 3rd party libraries. I will stop signing all 3rd things and

[WiX-users] Installing VSTO as pre-requisites from Bundle.wxs Failed

Hi,Hi, I've created a WIX (v3.7.0.0) installer for our VSTO application on Win 7 64 bit machine. Which do custom installation successfully. And I've also create Bundle.wxs file for installing the prerequisites for VSTO, like .Net Framework 4.0 client profile and VSTO 4.0. runtime. When I run

[WiX-users] Check that at least one Feature is selected

Hi all, I have a setup with feature selection enabled like this one now, in a file called MyInstaller.wxs, Feature Id=MyFeature Title=MyTitle Description=Desc Level=1 AllowAdvertise=no Absent=allow TypicalDefault=install

Re: [WiX-users] Check that at least one Feature is selected

Currently, there is limited scoping of properties in Wix 3.x. The only problem you may sometimes run into is when a property crosses the UI to Execute boundary--to do that, you'll need a public secure property. So, how exactly do you want to access MyFeature? -- John Merryweather Cooper

Re: [WiX-users] Check that at least one Feature is selected

I need to access MyFeature in the UserInterface code to make a condition such that if no feature is selected for installation the Next button can be disabled. Thanks and Regards, Noel From: jocoo...@jackhenry.com To: wix-users@lists.sourceforge.net Date: Mon, 15 Sep 2014 12:24:04 +

[WiX-users] Uninstallation failure due to admin rights

Hi, I'm using a wix custom Bootstrapper for installing and uninstalling my application. During uninstallation i've accessing the registry keys. But the uninstallation doesn't work properly due to registry access failure.But using the same registry accessing code in an console application in

Re: [WiX-users] Check that at least one Feature is selected

I solved this same issue with a custom action on the next button of the feature selection dialog. I tried solving it within Wix/Windows Installer but was unable to. The pseudo-code is something like this... Publish Dialog=CustomizeDlg Control=Next Event=DoAction Value=CAMustSelectOne

[WiX-users] LGHT0284: Support for more than 260 characthers in Path?

I thought Windows supports more than 260 characters by now? According to this: http://msdn.microsoft.com/en-us/library/windows/desktop/aa365247(v=vs.85).aspx#maxpath We run into path problems way to often with this.. -- View this message in context:

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

It's not a Windows issue, it's a .NET issue. -- John Merryweather Cooper Senior Software Engineer | Enterprise Service Applications | Continuing Development Jack Henry Associates, Inc.® | Lenexa, KS  66214 | Ext: 431050 |jocoo...@jackhenry.com -Original Message- From: neslekkim

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

The Visual Studio Limit is still 260. I don't think that Wix should go greater than 260 when the IDE has issues... Carter Quoting neslekkim asbj...@neslekkim.net: I thought Windows supports more than 260 characters by now? According to this:

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

Visual Studio?, What have that to do with this? MSBuild is building the project, if MSBuild also have an issue, that's another thing, this is in the linking phase, not during authoring of the wixfiles.. And who is using visualstudio for authoring wix projects anyhow?, absolutely no help in using

Re: [WiX-users] Custom action issue when msi is generated on Windows 8.1 and installed on Windows 8 or Windows 7

Hi, I used RemoveFolderEx as suggested. But I am still facing the same issue. The msi when generated on Windows 8.1 system runs fine and uninstalls fine on other Windows 8.1 systems. But it does not uninstall on Windows 8 or Windows 7 system. Directory Id='LocalAppDataFolder' Name='AppData'

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

Does prepending the path with \\?\ help out at all? http://blogs.msdn.com/b/bclteam/archive/2007/02/13/long-paths-in-net-part-1-of-3-kim-hamilton.aspx Stephen Tunney Nuance Communications, Inc. Solutions Architect, Imaging Division Waterloo, Ontario, Canada stephen.tun...@nuance.com

Re: [WiX-users] Custom action issue when msi is generated on Windows 8.1 and installed on Windows 8 or Windows 7

Hi, I had a similar issue, what i did was remove each file from the folder and then remove the folder. From: sharada.b...@outlook.com To: wix-users@lists.sourceforge.net Date: Mon, 15 Sep 2014 13:51:02 + Subject: Re: [WiX-users] Custom action issue when msi is generated on Windows

Re: [WiX-users] Issue in roll back on installation

That doesn't sound right. Rollback should rollback. Log file should tell all. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Mohamed Yasir

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

Win32 pretty consistently supports that syntax. .NET Framework pretty consistently does not. IIRC, Windows Installer API never supports it. IOW, we are mostly SOL. _ Short replies here. Complete answers over there:

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

So, if Windows Installer api does not support it, does that mean that Light would not work? on the workstations where we develop and build, it works ok, but on the buildserver, since it's scoping the output from versioncontrol for each build, it crashes from time to time, very annoying, and this

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

Jenkins, we have shortened several times now, also customize the wixproj file so intermediate files are going to obj instead of obj\Release, and so on. But it doesnt help that Wix creates those very long-named intermediate files, 65 characters for one file, and we have already shortened the

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

What are you using for a CI engine? Jenkins and CruiseControl.NET allow for doing custom workspace roots that can help shorten your path lengths. Stephen Tunney Nuance Communications, Inc. Solutions Architect, Imaging Division Waterloo, Ontario, Canada stephen.tun...@nuance.com 519-880-7463

Re: [WiX-users] LGHT0284: Support for more than 260 characthers inPath?

I for one am using Visual Studio to author and build my WiX projects. Why? Because all of my other projects are part of the same Visual Studio solution as my WiX projects. -Original Message- From: Asbjørn Mikkelsen Sent: Monday, September 15, 2014 09:14 To: General discussion about the

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

Right. This has come up many times. If we could fix it reasonably*, we would. * Technically speaking we could probably rewrite everything to just use Win32 APIs and do all kinds of moving files from short paths to long paths to work around MSI API limitations... but that would make the code a

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

As does TFS... -Original Message- From: Tunney, Stephen [mailto:stephen.tun...@nuance.com] Sent: Monday, September 15, 2014 10:42 AM To: General discussion about the WiX toolset. Subject: Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path? What are you using for a

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

What sort of filenames are the issue? We may be able to generate them differently depending on what they are. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Asbjørn

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

As mentioned earlier, it's theintermediate files, in the obj\release folder files are names as projectfilenamewithextension.Bind...FileListlanguagecode.txt for instance In one project that gave me an filename for one of the files tha tis 76 characters long. Yes, the projectfilename with exension

Re: [WiX-users] LGHT0284: Support for more than 260 characthers in Path?

We could make those binder data file paths shorter in WiX v4.0. _ Short replies here. Complete answers over there: http://www.firegiant.com/ -Original Message- From: Asbjørn Mikkelsen [mailto:asbj...@neslekkim.net] Sent:

Re: [WiX-users] Burn FileSearch in 64 bit system folder

Thanks for the responses. In particular, I didn't realize the newer redist packages can be safely run without detecting them before-hand. It seems like this could still be a problem for people who are not compressing the redists, but that is not my scenario. I also discovered this blog post which

[WiX-users] XmlConfig issue with Repair

Hi guys, I have an installer that's taking a password as input, and with that password creating an encrypted connection string. I'm using XmlConfig elements to dynamically insert the encrypted string into the application's config file. Install is working fine but Repair is creating an encrypted