wixedit-users Mailing List for WixEdit
Project moved to Github: https://github.com/WixEdit/WixEdit
Brought to you by:
jaykee
You can subscribe to this list here.
2006 |
Jan
|
Feb
(7) |
Mar
(6) |
Apr
(2) |
May
(6) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2007 |
Jan
(4) |
Feb
|
Mar
(3) |
Apr
|
May
(7) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2010 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
(2) |
Jun
(2) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2013 |
Jan
(2) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Roberto A. <rob...@gm...> - 2014-03-27 19:23:01
|
Hi everybody ! .. I have some wix (installer.wxs) wich compiles fine, and produces the corresponding intaller.msi. This installer works perfectly well in Windows XP/7 32 bits .. making thins like, copying files, setting registry, desktop icons, path's .. *But if, I run the same installer.msi under Windows 7 64 bits, then 'registry part' does not work (ie, it doesen't write any values to the Windows 7 64 registry)* Why is that ?? Help !! .. :-) Thanks in advance ! Rober |
From: Helge K. <Hel...@gm...> - 2013-02-19 13:29:51
|
Hello, I need to use FirewallExtension in my MSM and added the schema in the <Wix> node. xmlns:fire="http://schemas.microsoft.com/wix/FirewallExtension" But I get the error message "Namespace prefix 'firewall' is not defined." When I compile the .wxs at command line I get another error, when I omit the reference to the WixFirewallExtension.dll: error CNDL0200 : The File element contains an unhandled extension element 'fire:FirewallException'. To use the extension I have to add -ext "Path\To\WixFirewallExtension.dll" to use this extension. How do I work with Extensions in WiXEdit? What is the relation between the fire: namespace specified in the <Wix> node and the "firewall" prefix in the WiXEdit error message? The WiXEdit Edit Settings dialog has a default value "<projectfile>" -out "<projectname>.wixobj" <extensions> Can I somewhere define the extensions that WiXEdit should add to the candle command line? Regards Helge |
From: Jasper K. <jk...@gm...> - 2013-01-31 13:10:31
|
Hello Tim, Sorry for the delayed response, but I was temporary offline due to illness. WixEdit is just the editor. It makes WiX more visual and easier to comprehend and edit. The fancy stuff is really done by WiX, so that is what you should try to master. Unfortunately there is no tutorial for WixEdit. About the path environment variable, the WiX tutorial explains it exactly: http://wix.tramontana.co.hu/tutorial/com-expression-syntax-miscellanea/environmentally-friendly So in WixEdit, that means you should create an "environment" element, just within a component. (The same place where files are created.) And for the rest, follow the tutorial. Best regards, Jasper On Sun, Jan 27, 2013 at 3:44 AM, Tim Juntunen <tim...@gm...>wrote: > Noob question: > What is the best practice for appending a value to the the %path% > environmental variable in WiX Edit? > > I don't really understand the use of the properties, actions and tables > well. Is there a tutorial written for WiXEdit (I see that the WIX tutorial > is linked to the help menu item in WiXEdit, I was hoping to find a tutorial > written with screen shots from WiXedit.) > > Tim Juntunen > Darwin, MN, USA > > > ------------------------------------------------------------------------------ > 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 and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnnow-d2d > _______________________________________________ > Wixedit-users mailing list > Wix...@li... > https://lists.sourceforge.net/lists/listinfo/wixedit-users > > |
From: Tim J. <tim...@gm...> - 2013-01-27 02:45:03
|
Noob question: What is the best practice for appending a value to the the %path% environmental variable in WiX Edit? I don't really understand the use of the properties, actions and tables well. Is there a tutorial written for WiXEdit (I see that the WIX tutorial is linked to the help menu item in WiXEdit, I was hoping to find a tutorial written with screen shots from WiXedit.) Tim Juntunen Darwin, MN, USA |
From: Chris L. <chr...@at...> - 2012-01-27 17:14:34
|
Hello Just a quick heads up….. Some changes in my installer have now meant I need to use Burn. This means upgrading from Wix 3.0 to Wix3.6. So far this has been pretty painless except I got this warning warning CNDL1138 : The RegistryKey/@Action attribute has been deprecated. In most cases, you can simply omit @Action. If you need to force Windows Installer to create an empty key or recursively the key, use the ForceCreateOnInstall or ForceDeleteOnUninstall attributes instead. Long story short, I found what I was looking for BUT the online manual has two registry element pages (I didn’t realize this at first). One for V3.0 and one for V3.6. I have both V3.6 and V3.0 installed on the same machine in different folders but the help file opened via the shortcut under Wix 3.6 still appears to have the Registry element information from V3.0 in it. All the best Chris Lord |
From: Chris L. <chr...@at...> - 2012-01-26 17:13:49
|
Hello, I’ve been using WixEdit for several years and it’s a great little program. My original installer is fairly straight forward and so far WixEdit has been up to the task. However, things are now getting slightly more complicated and I need to author a bootstrapper using the Burn tool in the latest revision of Wix (V3.6). The files Burn uses are in the same XML format as used by Wix itself. I’m using WixEdit V0.7.5 and it can read the file no problem but it obviously doesn’t fully support Burn as there are properties missing. So….. 1) Can the current version support properties for Burn and if so, what do I need to do to make it do it? 2) If it can’t, can support for Burn files and bootstrapper creation be added? All the best and keep up the great work Chris Lord |
From: Jasper K. <jk...@gm...> - 2011-09-19 08:43:47
|
Hi Ken, The Wizard does not contain all functionality of WixEdit. For now you only can create a virtual directory. You should use WixEdit for the web application stuff. I agree the total lack of documentation is sad, but I don't know anybody who wants to write some for WixEdit. I hope you find your way with WixEdit without the documentation. Regards, Jasper On Wed, Sep 14, 2011 at 21:36, <Ken...@su...> wrote: > When using the Wizard to create a new project, where do I define the > folder where I want the source files of my web app to import and where do I > define the publish files and folders in the SourceDir\PFiles structure? > You’ve got lots of help for WiX in your app and literally none on WiX Edit. > **** > > ** ** > > Ken Jinks**** > > ** ** > > > ------------------------------------------------------------------------------ > BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA > Learn about the latest advances in developing for the > BlackBerry® mobile platform with sessions, labs & more. > See new tools and technologies. Register for BlackBerry® DevCon today! > http://p.sf.net/sfu/rim-devcon-copy1 > _______________________________________________ > Wixedit-users mailing list > Wix...@li... > https://lists.sourceforge.net/lists/listinfo/wixedit-users > > |
From: <Ken...@su...> - 2011-09-14 19:38:53
|
When using the Wizard to create a new project, where do I define the folder where I want the source files of my web app to import and where do I define the publish files and folders in the SourceDir\PFiles structure? You've got lots of help for WiX in your app and literally none on WiX Edit. Ken Jinks |
From: Jasper K. <jk...@gm...> - 2011-05-27 11:57:09
|
Hi Dominik, I guess you have to do some more advanced things in WiX. Please read the following: http://www.tramontana.co.hu/wix/lesson2.php#2.5 WixEdit does not support fragments, so if you want to use WixEdit, you should work around that by putting the elements in the main wxs file in one UI-element. I hope this helps. Regards, Jasper On Thu, May 26, 2011 at 12:12, Dominik Ohnezeit < dom...@ti...> wrote: > Hi, > > I'm new to WixEdit and I wanted to know how it is possible to customize the > Dialogs in the templates. > If I add a template (e.g. wix_mondo) I can't customize the dialogs. > > I can't customize anything... I think I'm too stupid. :-) > > Greets, > DomiOh > > > > ------------------------------------------------------------------------------ > vRanger cuts backup time in half-while increasing security. > With the market-leading solution for virtual backup and recovery, > you get blazing-fast, flexible, and affordable data protection. > Download your free trial now. > http://p.sf.net/sfu/quest-d2dcopy1 > _______________________________________________ > Wixedit-users mailing list > Wix...@li... > https://lists.sourceforge.net/lists/listinfo/wixedit-users > > |
From: Dominik O. <dom...@ti...> - 2011-05-26 10:50:39
|
Hi, I'm new to WixEdit and I wanted to know how it is possible to customize the Dialogs in the templates. If I add a template (e.g. wix_mondo) I can't customize the dialogs. I can't customize anything... I think I'm too stupid. :-) Greets, DomiOh |
From: Jasper K. <jk...@gm...> - 2010-09-21 08:11:41
|
Hi Akshi, This something that you should do in the xml directly. WixEdit supports the includes (loading and editing), but it is not possible to add the include with WixEdit. Regards, Jasper On Tue, Sep 21, 2010 at 08:09, Akshi Gupta <aks...@ad...> wrote: > Hi All, > > > > I read that including .wxi file through WixEdit in a .wxs file is a new > feature but I didn’t find this functionality. Can anyone tell me the way to > accomplish this? > > > > Thanks, > > Akshi > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Wixedit-users mailing list > Wix...@li... > https://lists.sourceforge.net/lists/listinfo/wixedit-users > > |
From: Akshi G. <aks...@ad...> - 2010-09-21 06:13:51
|
Hi All, I read that including .wxi file through WixEdit in a .wxs file is a new feature but I didn't find this functionality. Can anyone tell me the way to accomplish this? Thanks, Akshi |
From: Jasper K. <jk...@gm...> - 2010-06-30 08:17:20
|
Hi Ivo, Sorry for the late response. The publish events are usually child elements of the control. <Control Id="Next" Type="PushButton" ...> <Publish Event="NewDialog" Value="...">1</Publish> </Control> I see you are defining the events from a different location and referring to a control. Currently there is no way to add/edit events like the way you do. WixEdit won't remove your publish element upon load/save. It should leave elements as they are, except if they are a child element of an element that you deleted. I'll look into a way to support publish elements that are not child elements of a control. Regards, Jasper On Tue, Jun 22, 2010 at 20:48, <iv...@ro...> wrote: > Hi > > I am editing a setup project with WixEdit. I followed the instructions from > the "How To: Run the Installed Application After Setup" topic and now I have > this in my file: > <UI> > <Publish Dialog="ExitDialog" > Control="Finish" > Event="DoAction" > Value="LaunchApplication">WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and > NOT Installed</Publish> > </UI> > > I can't find the Publilsh item anywhere in the editor. Is it not supported? > If not, is it at least guaranteed to be preserved during load/save? > > Thanks > Ivo > > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Wixedit-users mailing list > Wix...@li... > https://lists.sourceforge.net/lists/listinfo/wixedit-users > |
From: <iv...@ro...> - 2010-06-22 18:48:20
|
Hi I am editing a setup project with WixEdit. I followed the instructions from the "How To: Run the Installed Application After Setup" topic and now I have this in my file: <UI> <Publish Dialog="ExitDialog" Control="Finish" Event="DoAction" Value="LaunchApplication">WIXUI_EXITDIALOGOPTIONALCHECKBOX = 1 and NOT Installed</Publish> </UI> I can't find the Publilsh item anywhere in the editor. Is it not supported? If not, is it at least guaranteed to be preserved during load/save? Thanks Ivo |
From: Jasper K. <jk...@gm...> - 2010-05-27 11:27:06
|
Hi, >From the xsd's in the doc directory, WixEdit determines which namespaces are used, and adds the correct extensions to the -ext argument. WixEdit also uses the xsd's to determine what elements can be created from the extension and where they can be used. For example from the Util namespace, the User element can be added as sub element of a Product element. Like this: <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:util=" http://schemas.microsoft.com/wix/UtilExtension"> <Product ...> <util:User ... /> </Product> </Wix> For the UI extension, WixEdit checks for UIRef elements and does not require any xsd. It seems you are using a <CustomAction BinaryKey="WixCA" ... /> which also requires an extension to be added to the commandline. WixEdit is not (yet) able to determine which extensions to add from CustomActions. It would be nice indeed to have some documentation for WixEdit... Regards, Jasper On Thu, May 27, 2010 at 11:53, Armin Linder <arm...@ar...>wrote: > Hi WixEdit users, > > I am using 0.7.3.3, and came across the following problem: > > I tried to author a msi which uses WixUIExtension and WixUtilExtension. > > Light won't run through because of "Unresolved reference to symbol > 'Binary:WixCA' in section 'Product:*'". After some research I found, > that I need to add a reference to the WixUtilExtension library using the > -ext command line switch for light.exe. > > This is odd, because in the documentation on page > > http://wixedit.sourceforge.net/ > > it says: > > "The use of the WiX extensions is really easy and blends in with the > standard functionality. You only have to point WixEdit to the directory > containing the XML Schema Definitions (XSD) of the extensions, which are > located in the /doc sub directory of the WiX installation." > > Some instructions about *how* to "pont WixEdit to the directory ..." > would really be helpful. After flipping through all the WixEdit dialogs > I finally found the "Locations" list in the "Tools" - "Options" dialog, > and the Xsds setting seemed promising, but alas, it alredy pointed to > the /doc subdirectory of the WiX toolkit which came with WixEdit > (3.0.5419.0), and changing it to point to the lates WiX build > (C:\Program Files\Windows Installer XML v3\doc) didn't change anything > either. Manually changing the Candle and Light command lines to "Custom" > using the "Build" - "Settings" dialog worked, however this does not at > all match what is written on the above page. > > Looking closer into the problem revealed, that WixEdit did indeed add > the -ext WixUIExtension switch, but forgot the -ext WixUtilExtension > switch. I suspected that there was probably due to an Xsd file/entry > missing in the /doc directory, and indeed, there wasn't any file which > lokked like it matched, but searching all the xsd files for > "WixUIExtension" revealed no hits as well. So it seems that the contents > of the doc directory isn't directly related to those two Wix extensions. > > Am I missing something, or is this a bug in WixEdit? > > Thanks, > > AL > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Wixedit-users mailing list > Wix...@li... > https://lists.sourceforge.net/lists/listinfo/wixedit-users > |
From: Armin L. <arm...@ar...> - 2010-05-27 10:09:41
|
Hi WixEdit users, I am using 0.7.3.3, and came across the following problem: I tried to author a msi which uses WixUIExtension and WixUtilExtension. Light won't run through because of "Unresolved reference to symbol 'Binary:WixCA' in section 'Product:*'". After some research I found, that I need to add a reference to the WixUtilExtension library using the -ext command line switch for light.exe. This is odd, because in the documentation on page http://wixedit.sourceforge.net/ it says: "The use of the WiX extensions is really easy and blends in with the standard functionality. You only have to point WixEdit to the directory containing the XML Schema Definitions (XSD) of the extensions, which are located in the /doc sub directory of the WiX installation." Some instructions about *how* to "pont WixEdit to the directory ..." would really be helpful. After flipping through all the WixEdit dialogs I finally found the "Locations" list in the "Tools" - "Options" dialog, and the Xsds setting seemed promising, but alas, it alredy pointed to the /doc subdirectory of the WiX toolkit which came with WixEdit (3.0.5419.0), and changing it to point to the lates WiX build (C:\Program Files\Windows Installer XML v3\doc) didn't change anything either. Manually changing the Candle and Light command lines to "Custom" using the "Build" - "Settings" dialog worked, however this does not at all match what is written on the above page. Looking closer into the problem revealed, that WixEdit did indeed add the -ext WixUIExtension switch, but forgot the -ext WixUtilExtension switch. I suspected that there was probably due to an Xsd file/entry missing in the /doc directory, and indeed, there wasn't any file which lokked like it matched, but searching all the xsd files for "WixUIExtension" revealed no hits as well. So it seems that the contents of the doc directory isn't directly related to those two Wix extensions. Am I missing something, or is this a bug in WixEdit? Thanks, AL |
From: Jasper K. <jk...@gm...> - 2010-02-23 08:32:44
|
Hi Armin, The link you've provided does keep some steps unclear. It uses fragments, but those are still not supported by WixEdit... WixEdit is only an editor for the XML of WiX, so all the nice UI features are part of the WiX toolkit. I've found this sample and this looks really complete and easy. It even provides a complete sample: http://www.wixwiki.com/index.php?title=WixUI_Custom This option indeed replaces the complete dialog... (you could get the original dialog you want to modify from the WiX sources) Another point, the DialogRef element the sample uses is not supported in WixEdit. Another (not so elegant) way of customizing your dialogs is, decompiling your msi with dark.exe and then modify the result. This is the way I've customized the WixEdit installation for adding a checkbox in the finish-dialog (a long time before WixUI was available). But this way you become responsible for the complete UI, instead of relying on the WiX team improving/fixing the dialogs in WixUI. I think this should help you with your custom dialog. I'll look into a way to make customizing dialogs or adding custom dialogs easier with WixEdit... Regards, Jasper On Tue, Feb 23, 2010 at 12:22 AM, Armin Linder <arm...@ar...>wrote: > Hi all, > > I don't use Visual Studio for my current project, but Borland Delphi. I > managed to write an msi installer for it using the Wix Editor, and the > command line tools (candle.exe and light.exe). > > I want to add two checkboxes to the ExitDialog in the WixUI_Featuretree > dialog sequence. While I found some bits of information about how to > customize the dialog definition files (like, e.g. > > http://www.dizzymonkeydesign.com/blog/misc/adding-and-customizing-dlgs-in-wix-3 > ), > there is no information about how to include the modified files into my > setup. I didn't even find out wether this is possible at all, without > recompiling the Wix Toolkit. > > Options I can think of are: modify the existing dialog, or replacing the > entire dialog with one of my own. > > Unfortunately I found no info/refernece/howto which explains, from > ground up, how the dialog definition system works, and how the defaults > can be superseeded/replaced/modified or whatever sich a mechanism would > be called by the creators. To be honest, I even failed to find out > wether the dialogs used by WixUI_FeatureTree (the dialog system I use > right now) are a feature of Wixedit or the Wix Toolkit or both, so I > have no idea where to start looking. > > Any help welcome, > > Armin. > > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Wixedit-users mailing list > Wix...@li... > https://lists.sourceforge.net/lists/listinfo/wixedit-users > |
From: Armin L. <arm...@ar...> - 2010-02-22 23:38:58
|
Hi all, I don't use Visual Studio for my current project, but Borland Delphi. I managed to write an msi installer for it using the Wix Editor, and the command line tools (candle.exe and light.exe). I want to add two checkboxes to the ExitDialog in the WixUI_Featuretree dialog sequence. While I found some bits of information about how to customize the dialog definition files (like, e.g. http://www.dizzymonkeydesign.com/blog/misc/adding-and-customizing-dlgs-in-wix-3), there is no information about how to include the modified files into my setup. I didn't even find out wether this is possible at all, without recompiling the Wix Toolkit. Options I can think of are: modify the existing dialog, or replacing the entire dialog with one of my own. Unfortunately I found no info/refernece/howto which explains, from ground up, how the dialog definition system works, and how the defaults can be superseeded/replaced/modified or whatever sich a mechanism would be called by the creators. To be honest, I even failed to find out wether the dialogs used by WixUI_FeatureTree (the dialog system I use right now) are a feature of Wixedit or the Wix Toolkit or both, so I have no idea where to start looking. Any help welcome, Armin. |
From: Jasper K. <jk...@gm...> - 2010-02-01 20:31:36
|
Hi, I've just release WixEdit v0.7.3. In this release the new wizard is really improved. It is the default and only way of creating new wxs files. It is really simple and with a few clicks the installer will have a: - Userinterface - Desktop Application Shortcut - Startmenu Application Shortcut - Startmenu Uninstall Shortcut - Startmenu Website Shortcut - and more... Thanks for reporting bugs! ... and please keep giving feedback on how to improve the wizard! Small installer samples are very welcome so I can create new templates for the wizard. Bye bye, Jasper |
From: Jasper K. <jk...@gm...> - 2009-08-05 20:59:22
|
Hi, Just release WixEdit v0.7.2.3 because it fixes an error while trying to save new .wxs files. Thanks for reporting! Regards, Jasper |
From: Jasper K. <jk...@gm...> - 2009-05-05 20:03:24
|
Hi, Just did some testing and WixEdit does not handle namespaces correctly when they differ from the default (that is the name of the XSD file). Make sure the namespaces match the XSD filename, so for "firewall.xsd" use "firewall" and not "fire" as namespace. I'll fix this in the next release. Thanks, Jasper On Tue, May 5, 2009 at 7:36 PM, Chris Lord <chr...@at...>wrote: > I had a working Wxs file I had been building using V0.6.1762. I need to > add a firewall exception when installing onto a Vista machine. In order to > do so I need to alter the schema line. > > Normally this reads > <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> > > but it now reads > <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:fire=" > http://schemas.microsoft.com/wix/FirewallExtension"> > > While WixEdit opens the file without any problems, the moment you try and > open the build menu, you get an error box appear. The menu never appears so > I am unable to build the install. > > The error states > Error Message: Namespace prefix "firewall" is not defined. > > If I build by running Candle and light from the command prompt, the file > builds the MSI without any errors. > > I have checked the docs directory and firewall.xsd is there and WixEdit > setup points to the correct folder. > > What did I miss? > > Thanks > > Chris Lord > > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK > i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > Wixedit-users mailing list > Wix...@li... > https://lists.sourceforge.net/lists/listinfo/wixedit-users > > |
From: Chris L. <chr...@at...> - 2009-05-05 17:36:36
|
I had a working Wxs file I had been building using V0.6.1762. I need to add a firewall exception when installing onto a Vista machine. In order to do so I need to alter the schema line. Normally this reads <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> but it now reads <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi" xmlns:fire="http://schemas.microsoft.com/wix/FirewallExtension"> While WixEdit opens the file without any problems, the moment you try and open the build menu, you get an error box appear. The menu never appears so I am unable to build the install. The error states Error Message: Namespace prefix "firewall" is not defined. If I build by running Candle and light from the command prompt, the file builds the MSI without any errors. I have checked the docs directory and firewall.xsd is there and WixEdit setup points to the correct folder. What did I miss? Thanks Chris Lord |
From: Jasper K. <jk...@gm...> - 2009-05-01 09:12:58
|
Hi Ben, Sorry for the late reply. WixEdit does some automatic detection of used extensions, when extensions are used like <iis:...> or <util:....> Using the UI-extensions is not detected. I'll put this up as feature request. Thanks, Jasper On Wed, Apr 8, 2009 at 10:31 AM, Ben Charlton < ben...@as...> wrote: > I don’t think Wixedit correctly assigns some of the Wix v3 extensions…I > thought it was automatic. > > I want to use WixUI_mondo and create a UIREF to it…I would think that > wixedit would build the msi by adding –ext WixUIExtension to the commandline > as well as –culture:en-Us > > This doesn’t happen so I used a custom command line…is there an automated > where of wixedit does this > > > > Theinformation contained in the above email > message or message(which includes any attachments) is confidential and may be legally > privileged. It is intended only for the use of the person or entity > to which it is addressed. If you are not the addressee any form of > disclosure, copying, modification, distribution or any action taken > or omitted in reliance on the information is unauthorised. > > > > > ------------------------------ > Ph: 32682688 > Fax: 38681488 > > The views expressed in this email are those of the sender and may not equate to the views of the > Ascot Veterinary Surgery. > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by: > High Quality Requirements in a Collaborative Environment. > Download a free trial of Rational Requirements Composer Now! > http://p.sf.net/sfu/www-ibm-com > _______________________________________________ > Wixedit-users mailing list > Wix...@li... > https://lists.sourceforge.net/lists/listinfo/wixedit-users > > |
From: Ben C. <ben...@as...> - 2009-04-08 08:31:26
|
I dont think Wixedit correctly assigns some of the Wix v3 extensions I thought it was automatic. I want to use WixUI_mondo and create a UIREF to it I would think that wixedit would build the msi by adding ext WixUIExtension to the commandline as well as culture:en-Us This doesnt happen so I used a custom command line is there an automated where of wixedit does this Theinformation contained in the above email message or message(which includes any attachments) is confidential and may be legally privileged. It is intended only for the use of the person or entity to which it is addressed. If you are not the addressee any form of disclosure, copying, modification, distribution or any action taken or omitted in reliance on the information is unauthorised. Ph: 32682688 Fax: 38681488 The views expressed in this email are those of the sender and may not equate to the views of the Ascot Veterinary Surgery. |
From: Jasper K. <jk...@gm...> - 2008-08-09 11:19:56
|
Hi, Sorry for the late response, but I was on holiday this week. With Wix 3.0 WixEdit automatically determines the extensions used and adds them the commandline. (Extensions is not supported for Wix 2.0) WixEdit uses all xsd files located in the doc directory to determine all extensions. The default candle commandline: "<projectfile>" -out "<projectname>.wixobj" <extensions> Where the "<extensions>" part is replaced by all used extensions, like: "-ext WixcomplusExtension" When compiling a setup the output part of the results panel contains the complete commandlines used (See lines beginning with "----- Starting") and all the output of the commandline tools, so you can see what really happens. I hope this helps. Jasper On Fri, Aug 1, 2008 at 8:15 PM, Mo Benmouffok <mbe...@gm...> wrote: > Hi, > > I have several setups written in Wix 2.0 and 3.0. I'm currently in the > process of trying several Wix editors to facilitate deployment development. > I had a general question concerning WixEdit. How does it load extensions. > Does it have to be done by modifying the command-line or does it have some > kind of automatic loading of extensions. I currently hooked up the WixEdit > to Wix 3.0.4311.0, and I'am trying to compile a setup that need to use the > "WixComPlusExtension.dll". > > Thanks. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Wixedit-users mailing list > Wix...@li... > https://lists.sourceforge.net/lists/listinfo/wixedit-users > > |