Sorry Rob,
but I take that number version when I was drunk. May be 3.8.506.0 ?
Thanks.
2013/7/25 Rob Mensching r...@robmensching.com
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
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 I take that
Hello,
Having a bit of a problem doing this and not sure of it can be done. I have
an edit control that a user types into, I would like for the input to be all
in capital letters. I tried having a custom action on the edit control to
get the property, convert to capital letters and set the
I think the correct way is to chnage the order of your custom actions
and use conditions on components
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Install-files-dynamically-based-on-Config-changes-tp7587573p7587620.html
Sent from the
Thank you Rob for your detailed explanation, appreciated.
Then we can use burn and all its features without worry and set
DisableModify=yes DisableRemove=yes for the bundle to hide it in program
and features.
/ Tomas
-Original Message-
From: Rob Mensching
Yes, OK, thanks. I did that and was getting confused because my test was:
--- clean machine: install old addon
--- install new (incompatible) main bundle
I thought the addon should be removed (but it won't be since it's not related
to the new bundle). So then I thought I need to use an install
Yes, yes. smile/
On Fri, Jul 26, 2013 at 6:30 AM, Wesley Manning wmann...@dynagen.ca wrote:
Yes, OK, thanks. I did that and was getting confused because my test was:
--- clean machine: install old addon
--- install new (incompatible) main bundle
I thought the addon should be removed (but
Is it possible to get feedback from light (or any of the other WiX binaries)
what it is currently doing (e.g. compressing file XY) or even something
like 37% finished?
(Verbose output is only a slight improvement as it stays rather long at
Creating cabinet.)
--
View this message in context:
Hi Steve,
After googling more I found that I needed to add reference
WixCommonUiExtension.dll to my WiX 3.6 project in Visual Studio 2010. However,
as I did so, I got error that WixCommonUiExtension.dll is not a valid WiX
reference. How can resolve this issue?
Thanks a lot!
Miaohsi
Classification: Public
I have 5 custom dialogs that I created that I use in my WIX project, I didn't
need to reference that...
Steve
-Original Message-
From: Wang, Miaohsi [mailto:miaohsi.w...@invensys.com]
Sent: July-26-13 1:01 PM
To: General discussion for Windows Installer XML
I have used HeatFile in my setup project to harvest a dll for register it for
COMIf I build my project in Debug mode I have this:
Component Id=cmpA8B0842041500B0ACE61F7EFD0FBD893
Directory=dir0F6F75DF46D1BACE2233EC573E6D4AA9 Guid=PUT-GUID-HERE
File Id=myFile.dll KeyPath=yes
SelectDbDialog is not a dialog I recognize as supplied by WiX in the
WixUIExtension. You need to find the source of that dialog and include it in
your build (your error simply indicates that the dialog sources were not found
in any object, library, or extension.
Steven Ogilvie
Right now there is only verbose. You could open a feature request or even
contribute a solution.
MrWiX philipp.ew...@asamnet.de wrote:
Is it possible to get feedback from light (or any of the other WiX binaries)
what it is currently doing (e.g. compressing file XY) or even something
like 37%
How are you calling HeatFile?
Marco Tognacci mark...@live.it wrote:
I have used HeatFile in my setup project to harvest a dll for register it for
COMIf I build my project in Debug mode I have this:
Component Id=cmpA8B0842041500B0ACE61F7EFD0FBD893
I would note that most progress displays play havoc with IDE's trying to parse
error messages. Most compilers don't have them for that reason. The last
compiler I had that had such a progress display was Meridian Ada DOS and that
is more than twenty years ago now.
--
John Merryweather Cooper
I have added a node in the setup project in the Before build sections
Target Name=BeforeBuild
HeatFile File=..\distribution\Bin\$(Configuration)
PreprocessorVariable=var.HarvestPath
OutputFile=HeatGeneratedFile.wxs
ComponentGroupName=HeatGenerated
I would expect DirectoryRefId to match the Directory@Id you're substituting.
However, this should cause it to break in both Configurations, so I suspect
that's not it.
Is this Release configuration build breaking on a build server, both locally
and on a build server, or just locally? I note
The directory is fine, I build it locally and on a build server, the fact that
I can't figure out is why I have 2 different results building Debug or Release.
I have tried to fix the path not using $(Configuration) but it seem make no
difference.
From: jocoo...@jackhenry.com
To:
I also suggest you do a regsvr32 on your release DLL and ensure that the
codebase value in the registry is correct.
Also check your build spew to double check the command line passed to the heat
utility.
John Cooper jocoo...@jackhenry.com wrote:
I would expect DirectoryRefId to match the
I prefer not to run exe files for registring dll during installation, I'd like
to add only the registry keys that I need, and make it with the msi.As I have
made in debug works but I can't figure out why in Release don't work.Perhaps a
bug in the Heat.exe ???
Date: Fri, 26 Jul 2013 14:03:12
Forgot to mention, I am using WiX 3.7.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Force-Update-of-Corrupt-KeyPath-File-tp7587628p7587636.html
Sent from the wix-users mailing list archive at Nabble.com.
I'm not recommending running an exe during installation. Instead I'm suggesting
taking that DLL you are passing to the heat tool and registering it into a VM
to double check what it is writing.
Marco Tognacci mark...@live.it wrote:
I prefer not to run exe files for registring dll during
I have checked it, registering it using a custom exe and using c#
RegistrationServices.RegisterAssembly, the line added to the registry are equal
to that harvested by Heat.I can't make it hard coded as I would change the
version and even if my dll will expose other interfaces.Using Heat I need
23 matches
Mail list logo
