of the redevelopment effort.
Not sure on the project leader part. What resources are available to
such a leader (types and experience of developers/testers/PMs, etc.)?
Blair
From: BGINFO4X
Sent: Friday, January 24, 2014 7:25 AM
Attending your experience, do you think that is possible to build
Dear Sirs.
Attending your experience, do you think that is possible to build an
installer like the traditional setup.exe installer from cygwin.com?
In the following url you can see the main screens.
http://x.cygwin.com/docs/ug/setup-cygwin-x-installing.html
I ask basically for the screens
/UtilExtension;
xmlns:netfx=http://schemas.microsoft.com/wix/NetFxExtension;
Product Name='BGINFO4X for Windows $(var.ProductVersion)' Id='*'
UpgradeCode=$(var.ProductUpgradeCode) Language='1033' Codepage='1252'
Version='$(var.ProductVersion)' Manufacturer='KZTSoftware'
!-- Main packed
and uninstalling? Do you have uninstall logs?
-Original Message-
From: BGINFO4X [mailto:bginf...@kztsoftware.com]
Sent: Thursday, October 24, 2013 10:23 AM
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Bug or wxs problem?
Hello,
I have a big problem
://schemas.microsoft.com/wix/NetFxExtension;
Product Name='BGINFO4X for Windows $(var.ProductVersion)' Id='*'
UpgradeCode=$(var.ProductUpgradeCode) Language='1033' Codepage='1252'
Version='$(var.ProductVersion)' Manufacturer='KZTSoftware'
!-- Main packed declaration --
Package Id='*' Keywords
.
DirectoryRef Id=Utils
Component Id=ApplicationShortcutHTML
Guid=BCD09B03-9EA8-4FAA-B920-
C04C95310E4C
Shortcut Id=ApplicationStartMenuShortcutHTML
Name=BGINFO4X - Html Report
Target=[\%]USERPROFILE[\%]\BGINFO4X\EXPORT\BGINFO4X.html/
RemoveFolder Id=Utils
Component Id=ApplicationShortcutHTML
Guid=BCD09B03-9EA8-4FAA-B920-
C04C95310E4C
Shortcut Id=ApplicationStartMenuShortcutHTML
Name=BGINFO4X - Html Report
Target=[\%]USERPROFILE[\%]\BGINFO4X\EXPORT\BGINFO4X.html/
RemoveFolder Id=Utils
-9EA8-4FAA-B920-
C04C95310E4C
Shortcut Id=ApplicationStartMenuShortcutHTML
Name=BGINFO4X - Html Report
Target=[\%]USERPROFILE[\%]\BGINFO4X\EXPORT\BGINFO4X.html/
RemoveFolder Id=Utils On=uninstall/
RegistryValue Root
= 9640CA85-6906-48E8-9ABB-801DBF37DEDB?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
xmlns:netfx=http://schemas.microsoft.com/wix/NetFxExtension;
Product Name='BGINFO4X for Windows $(var.ProductVersion)' Id='*'
UpgradeCode
= 3.0.8?
?define ProductUpgradeCode = 9640CA85-6906-48E8-9ABB-801DBF37DEDB?
Wix xmlns=http://schemas.microsoft.com/wix/2006/wi;
xmlns:util=http://schemas.microsoft.com/wix/UtilExtension;
xmlns:netfx=http://schemas.microsoft.com/wix/NetFxExtension;
Product Name='BGINFO4X
just what Windows does. This article is fairly old
but the general principle still applies:
http://blogs.msdn.com/b/oldnewthing/archive/2005/11/24/496690.aspx
Phil Wilson
On Mon, Sep 9, 2013 at 9:17 AM, BGINFO4X bginf...@kztsoftware.com wrote:
Hello, you are right.
The shortcut
://schemas.microsoft.com/wix/UtilExtension;
xmlns:netfx=http://schemas.microsoft.com/wix/NetFxExtension;
Product Name='BGINFO4X for Windows $(var.ProductVersion)' Id='*'
UpgradeCode=$(var.ProductUpgradeCode) Language='1033' Codepage='1252'
Version='$(var.ProductVersion)' Manufacturer='KZTSoftware
Hello,
Is there any way to tell WIX that when uninstalling the program,
uninstall a file ONLY if it has not been modified after the
installation?
That could be very useful for backing up config files,
Thanks a lot.
works well with -gg and doesn't work well with
-ag. If this is not a bug, why the -ag option fails with error
LGHT0230?
Thanks a lot for your time.
2013/5/28 BGINFO4X bginf...@kztsoftware.com:
Hello again, I need your help.
The problem with heat -ke + light seems to be related to the fact
-wix.aspx)
Thanks a lot for your time.
Regards.
2013/5/27 BGINFO4X bginf...@kztsoftware.com:
Hello everyone,
I'm already finish, , but I have a little problem related to the
NTFS Permissions:
The normal permissions inside %program files% are: Administrators -
FULL CONTROL ; Users - Read
-ag?
If I use -gg, light works, but here in the forum this option is not
recommended.
Can you confirm that this is a bug? I use the latest wix 3.8.520 version
If it is, I will open a bug in bug file site.
Thanks a lot.
2013/5/27 BGINFO4X bginf...@kztsoftware.com:
Hello,
I'm using HEAT
you have some recommendations?
Thanks a lot for your time.
2013/5/22 BGINFO4X bginf...@kztsoftware.com:
Ok, thanks a lot.
Regards.
2013/5/21 Mike Carlson corf...@gmail.com:
Ah, then you do want to support upgrades. Get your upgrade scenario right,
and you won't have to worry about having
Hello,
I'm using HEAT with the option -ke (keep empty directories) with the
following commands:
@echo off
echo
##
echo HEAT!
C:\Program Files\WiX Toolset v3.7\bin\heat dir BGINFO4XW -cg
SampleGroup -out SampleGroup.wxs
, May 21, 2013 at 9:34 AM, BGINFO4X bginf...@kztsoftware.com wrote:
2013/5/21 Mike Carlson corf...@gmail.com:
You should be able to. Create the shortcut in your own authoring file. To
point to the file in the generated authoring, see the Target attribute
of
the shortcut element in wix.chm
You should change it to this:
Directory Id='ProgramFilesFolder' Name='PFiles'
Directory Id='INSTALLDIR' Name='BGInfo4X for Windows
$(var.ProductVersion)'
Directory Id='basedir'/Directory
/Directory
/Directory
Thanks, it works!
Also, you should pass in -srd
2013/5/21 Mike Carlson corf...@gmail.com:
You should be able to. Create the shortcut in your own authoring file. To
point to the file in the generated authoring, see the Target attribute of
the shortcut element in wix.chm.
Thanks a lot , I will try it.
I have a conceptual question regarding
Hello everyone,
I'm a new to WIX and I'm a little lost.
I want to create a .msi file from my project (with lots of files and
folders), so I use HEAT.
Heat works as exepcted and a new file is created (SampleGroup.wxs).
Then I try to compile all : C:\Program Files\WiX Toolset
v3.7\bin\candle
='windows-1252'?
?define ProductVersion = 2.8.4?
?define ProductUpgradeCode = 9640CA85-6906-48E8-9ABB-801DBF37DEDB?
Wix xmlns='http://schemas.microsoft.com/wix/2006/wi'
Product Name='BGInfo4X Example $(var.ProductVersion)' Id='*'
UpgradeCode=$(var.ProductUpgradeCode) Language='1033'
Codepage='1252
2013/5/17 Jeremiahf jeremi...@gmail.com:
Ah, so your building your MSI via command line. Good to hear you figured it
out.
Yes, I'm doing only a .msi package, not a visual project with c# or similar ...
Thanks.
--
foo under INSTALLDIR (or wherever you want the files to show up).
Done:
Directory Id='ProgramFilesFolder' Name='PFiles'
Directory Id='INSTALLDIR' Name='BGInfo4X for Windows
$(var.ProductVersion)'/Directory
Directory Id='basedir'/Directory
/Directory
Well, ... the resulting .msi
25 matches
Mail list logo
