Re: [WiX-users] RE. Multilanguage bundle
Hi, I installed WiX3.8 and it did autodetect German language. BR, Branko -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RE-Multilanguage-bundle-tp7588097p7588286.html Sent from the wix-users mailing list archive at Nabble.com. -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RE. Multilanguage bundle
Hi, Ok, I'll try also the WiX3.8 to see how it works with language detection. Namely, I looked at the examples (though I haven't built them yet) of Extended BA and made accordingly but still auto language detection doesn't work. I also wanted to use localized Eula.rtf with Extended BA but unsuccessfully. It said there must be something wrong with the file Eula.rtf. I tried to reference the localization so: I tried different names (analogue to thm.wxl: License.rtf, LicenseFile.rtf etc.). I looked for it in the WixStandardBootstrapperApplication.cpp for expected name, but couldn't figure it out. Bundle11.wxs gives some hint but I was not successful. On the one hand we have Payloads and on the ohter WixVariable elements. Hm? I hope that switching to WiX3.8 really resolves my issue (simple uncomplicated installer with MsiPackage conditions only). I hope someone can help me with the License.rtf localization in Extended BA. Regards -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RE-Multilanguage-bundle-tp7588097p7588284.html Sent from the wix-users mailing list archive at Nabble.com. -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] RE. Multilanguage bundle
Phil, thx for your guidance so far. In WiX3.7 I manage to build setup.exe and run it with or without -lang 1031. So I can see English and German draft version. Now I wanted to get to auto detection on running setup.exe. So I downloaded the WixBalExtensionExt.dll. I used that in candle.exe (WixBalExtensionExt) and light.exe. In my .wxs I only changed the ...Standard... to ...Extension... I left .RtfLicense. I build it no problem. So as my native language is de - austrian german), I should see German version, but it is the same. I get it only with adding -lang 1031. I also downloaded your two .exe files seen in the previous post and it does run german version already from the start. What am I doing wrong. I am not using .HyperlinkLicense only .RtfLicense as before. BR ... -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RE-Multilanguage-bundle-tp7588097p7588253.html Sent from the wix-users mailing list archive at Nabble.com. -- Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] RE. Multilanguage bundle
Hi, It must have been something with copy&paste. Now it works. Thx. So, in WiX3.7 it is not possible yet to use detected language automatically? BR, Branko -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] RE. Multilanguage bundle
This is what Bundle's log sais: Error 0x8007006e: Failed to load loc file from path: ... \.ba1\1031\thm.wxl Error 0x8007006e: Failed to initialize data in bootstrapper application. BR, Branko -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multilanguage bundle
No, it doesn't work if I keep this line even in WiX 3.7: No errors but also no setup UI after calling setup.exe (with or without -lang 1031). I also tried with LicenseUrl='' and adding two additional elements for logo and theme in 1031 but also that didn't help. How to make setup.exe -lang 1031 to show up the installer with different eula? BR, B. -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multilanguage bundle
It must be it doesn't work in WiX 3.6. Ok, I have upgraded WiX to 3.7 and now the default .exe works as expected (now language specifics). But If I call the setup .exe file with language param (-lang 1031) it doesn't run but there is also no response whatsoever. BR, B. -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Multilanguage bundle
Hi, I am testing multilanguage bundle (burn) support but I couldn't make it work: ... ... Candle and light don't complain. When I run the resulting .exe nothing happens. If I remove the the element then the setup works as expected. When I define a theme under element as an ThemeFile the same happens - it doesn't run. I want to make Multilanguage bundle setup to be dependant on computer system selection or to enable user to decide (menu). Do I have to got to 3.8 for this purpose as I read in posts? Thx, B. -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Multilanguage bundle
Hi, I currently use WiX 3.6. BR, Branko -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] MsiPackage InstallCondition
I used thorougly DIFxApp instead of DPInst for device driver installation (subject: Installing a driver in Win 7) as you adviced. I used and tested the following InstallConditions: 1. "VersionNT64" for installing MsiPackage on x64 platforms and 2. "NOT VersionNT64" for installing on x86 platforms. The test went fine (I don't use the "Installed" condition). I still lack of a reference of Wix Bundle MsiPackage Install Conditions Value list and description. But finding some examples and learning by doing helped so far. BR, B. -- 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/learnmore_122712 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] MsiPackage InstallCondition
I've got two msi packages in a wix bundle. I want to install one on x86 platform and the other in case of x64 platform. Is it good if I need for the first case the following condition: "NOT VersionNT64" and for the second: "VersionNT64"? Can be used also "Installed AND ..." condition in this burn context? Where can I find all the condtions for MsiPackage? Thx -- Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery and much more. Keep your Java skills current with LearnJavaNow - 200+ hours of step-by-step video tutorials by Java experts. SALE $49.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122612 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] Installing a driver in Win 7
What do you mean by "machine path"? You probably mean I call the DPInst64.exe from system path, not from the installed folder. Yes, I checked and there really is one such file in DIFX folder. That could be it. -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Installing a driver in Win 7
I'm trying to make an installer using DPInst.exe as a CustomAction. Although there are some solutions provided, it fails. I can install the driver using rightclick on .inf and Install. I can even use manually DPInst.exe on installed folder. When I use Notepad.exe instead of DPInst.exe it works. Although DPInst.exe is inlcuded in the installed folder as DPInst64.exe. I can even achieve that Notepad opens our .inf file (provide parameter). The result of installing our .msi is the entry in ARP. In Device Manager the device is not properly installed. Seeing .log shows an error in using quiet mode, or nothing. My notion was, the path is somehow wrong. So, I tried to add "/path parameter" but still failed. I know I can try finally using but I still try using DPInst.exe to avoid taking care of 32- or 64-bits. Do you have any idea what could be wrong? These is my fragment of trials on "custom actions": The log says: CAQuietExec64: Error 0x80070002: Command failed to execute. CAQuietExec64: Error 0x80070002: CAQuietExec64 Failed Or DPInst64.exe There is no error but neither proper installation. Notepad.exe Here I had to provide path [SourceDir] or target [INSTALLDIR]\subfolder\some.inf ... NOT VersionNT64 VersionNT64 -- Master SQL Server Development, Administration, T-SQL, SSAS, SSIS, SSRS and more. Get SQL Server skills now (including 2012) with LearnDevNow - 200+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only - learn more at: http://p.sf.net/sfu/learnmore_122512 ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] Simple UI with license agreement
Hello, I would like to have a simple UI comprising Hello, EULA, and completion. Using UICommon is ok, but can't include the license agreement. Using UIInstallDir and UIFeatureTree have license but Can't exlude dir or custom dialogue. Do you have any hint how to proceed? Regards, Branko -- Got visibility? Most devs has no idea what their production app looks like. Find out how fast your code is with AppDynamics Lite. http://ad.doubleclick.net/clk;262219671;13503038;y? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] !(bind.FileVersion): LGHT0298 - unresolved bind-time variable
Hello, I am trying to bring a VS (2010) solution with one executable project and accompanied installer to build. It works on another machine which has targeted .NET framework 3.5 (so x86) and which uses WiX 3.5. On my similar platform (Win 7 x64) but with .NET framework 4.0 and WiX 3.6 encounter smaller problems. In my .wxs (why is not .wsx?), I have three times !(bind.FileVersion.PiepsDiagnosticV3.exe): ... Linker (light.exe) says in all this cases: D:\work\DesktopApps\Installer\Product.wxs(7,0): error LGHT0298: Unresolved bind-time variable !(bind.FileVersion.PiepsDiagnosticV3.exe). D:\work\DesktopApps\Installer\Product.wxs(30,0): error LGHT0298: Unresolved bind-time variable !(bind.FileVersion.PiepsDiagnosticV3.exe). D:\work\DesktopApps\Installer\Product.wxs(31,0): error LGHT0298: Unresolved bind-time variable !(bind.FileVersion.PiepsDiagnosticV3.exe). On the source project, there was even so: ... ... It seems to me wrong, but the in could be build. Thanks for any hint. Regards, Branko -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://ad.doubleclick.net/clk;258768047;13503038;j? http://info.appdynamics.com/FreeJavaPerformanceDownload.html ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix ftdi drivers
James, Mission completed!!! At least at this issue. Thx for the displacement tip. After that, from the log it was obvious there were missing files in missing amd64 directory. I looked into both .inf files and provided the 64bit directories (for both .inf files) and :-) the installer could successfully install the ftdi drivers. I am still a little bit confused, why the installer put the directories under C:\Program Files (x86) as it obviously demands x64 versions of files. But I'm fully satisfied with that so far. No, I can focus on finer stuff around WiX. I think I will even help with localization with Slovenian version of installer. James, thanks a lot for great help! Best regards, Branko P.S. For those who also need to install ftdi drivers on windows on your own (for instance you don't have Internet on the computer), via WiX ver. 3.6 I provide my experience bellow: I'm using such candle command: candle.exe -ext WixDifxAppExtension ftdiinstall.wsx Since my xml source of the wix is ftdiinstall.wsx (provided bellow). WixDifxAppExtension is extension, of course. Have a look also of the xml namespace int the root tag of the xml to reference on the preffixed tags as in my case. This command produces ftdiinstall.wixobj. Then I use the folllowing light.exe command: light.exe -ext WixDifxAppExtension difxapp_x64.wixlib ftdiinstall.wixobj -out ftdiinstall.msi ftdiinstall.wixobj is produces by candle.exe and the output is ftdiinstall.msi (it may be optional). You may need to include difxapp_x86 instead when you have 32-bit architecture of the computer. Since I didn't get explicit result reply if installation was successful or not, I had to check it (check the expected directories with copied driver files, check Add/remove apps under control panel if it was selected to be included there ( attributes), or just unplug the network cable and uninstall the drivers (via Device Manager - right click uninstall and checkbox on "delete files"; then use your installer and replug the device via USB). The finer way to check if something went wrong is using logging with installing (in this case you don't doubleclick the ftdiinstall.msi in my case but): msiexec /i ftdiinstall.msi /L* LogFile.txt /i means install (/x would mean uninstall) /L* means create full logging into LogFile.txt. I must emphasize I had all the needed files in the same directory as the installer files. Otherwise you would need the -b "path" for light.exe. And my ftdiinstall.wsx (wix source file) is as follows: Each directory has it's own . is only in the where .inf files are placed! Although both .inf files where in the same directory as apropriate for DSInstall.exe tool, for WiX each .inf file has to be placed in it's own directory, thus some files had to be copied to its own directory (before there were common directories: i386 and amd64). Altough I had to put some effort to come to the result (with the help of this mailing list and James) I learned a lot that way. And I will learn using WiX in the future too ;) . Regards, Branko Horvat -
Re: [WiX-users] wix ftdi drivers
My driver msi is now set to perMachine installation. When I comment both
tags, the files are actually copied into general "programFiles"
(not into user programFiles).
But when I uncomment Driver tag, this error occurrs (got from log file under
/L* switch):
...
DIFXAPP: ERROR: no driver packages found in C:\Program Files
(x86)\Pieps\FtdiDrivers\FtdiBusDriver\i386\
DIFXAPP: ERROR: InstallDriverPackages failed with error 0x2
...
DIFXAPP: ERROR: Unable to retrieve the driver store handle corresponding to
componentId '{5BE845A4-9787-4218-B578-22878B31231B}'
DIFXAPP: ERROR: Rollback failed with error 0x2
...
MSI (c) (00:F4) [15:55:53:473]: Product: FTDI Drivers Installer -- Installation
failed.
Otherwise my commands were:
candle.exe -ext WixDifxAppExtension ftdiinstall.wsx
light.exe -ext WixDifxAppExtension difxapp_x64.wixlib ftdiinstall.wixobj -out
ftdiinstall.msi
Both commands produced no errors!
As no dirvers were available as expected (when i unplug LAN network he doesn't
find drivers on plug&play the device)
I used the following command to get log entries.
msiexec /i ftdiinstall.msi /L* LogFile.txt
I can provide additional data if needed. I am available one more hour today.
Thx
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix ftdi drivers
James,
I realised the RemoveFolder tags are necesary because I am installint into
userprofile,
not for all users on a computer as I hope it want ask admin permission to
install.
If I remove difx:Driver tag then I can reproduce the file hierarchy - actually
not as originally is,
since there are two .inf in the same directory. And, as I read somewhere, each
driver must be
int seperate directory for wix (and thus also in a seperate component). I
solved it that way
that both created directories contain it's own subdirectory with x86 files
(originally it was common).
I took a look of all needed files in both inf. files.
So the bottom line is I can manage to procuse file hierarchy as I wish (as I
suppose is expected).
When I uncomment difx:Driver tags the same errors as till now:
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(33) : error LGHT0094 : Unresolved ref
erence to symbol 'CustomAction:MsiProcessDrivers' in section 'Product:{E00E5A99-
913D-4C68-98BF-B43A471CD45D}'.
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(53) : error LGHT0094 : Unresolved ref
erence to symbol 'CustomAction:MsiProcessDrivers' in section 'Product:{E00E5A99-
913D-4C68-98BF-B43A471CD45D}'.
This is when I use: light.exe -ext WixDifxAppExtension ftdiinstall.wixobj
When I use:
C:\Users\hob\Documents\WiX>light.exe -ext WixDifxAppExtension
-ext "D:\tmp\ftdi\difxapp_x86.wixlib" ftdiinstall.wixobj
(you see I even tried with absolute path)
it says:
light.exe : error LGHT0144 : The extension 'D:\tmp\ftdi\difxapp_x86.wixlib'
could not be loaded because of the following reason:
Could not load file or assembly 'file:///D:\tmp\ftdi\difxapp_x86.wixlib'
or one of its dependencies.
The module was expected to contain an assembly manifest.
This makes me think this is for .net environment.
--
Got visibility?
Most devs has no idea what their production app looks like.
Find out how fast your code is with AppDynamics Lite.
http://ad.doubleclick.net/clk;262219671;13503038;y?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wix ftdi drivers
>Some comments below; they may not fix your problem, but point to other >issues in the WXS: Thanx for all your hints! > >> -Original Message- >> From: Branko Horvat [mailto:branko_horvat@...] >> Sent: Wednesday, September 12, 2012 09:27 >> To: wix-users@... >> Subject: [WiX-users] wix ftdi drivers >> >> C:\Users\hob\Documents\WiX\ftdiinstall.wsx(29) >> C:\Users\hob\Documents\WiX\ftdiinstall.wsx(42) > >The WSX you attached got cut off at various points, can you show which lines >of code were indicated by the faulty lines #29 and #42? Both difx:Driver tags are referred to: > >> >> >> >> > >You don't need to have RemoveFolder. This element can be completely >removed. The directories you create will be removed anyway on uninstall. > >This is true for all instances of RemoveFolder in your example code. > I didn't have it at the beginning. But compiler (candle.exe) demanded it (maybe I didn't have components at that time yet). Also the keyValues was demanded at the same time (it said a keyValue must exist not a file), if I am not mistaken. So, I've removed it and now it looks fine. Thanx!!! >> > PlugAndPlayPrompt='no' ForceInstall='yes' /> > >I would suggest changing "ForceInstall" to "no". If you set it to "yes" >like in your example, you could force downgrading the driver to an older >version if the user's system had a newer version of the driver installed. >That may cause compatibility problems with other software and devices >installed on the customer's computer that also uses an FTDI driver. > Ok, I've changed it to 'no'. >> >> >> > >You can't install files in a component into multiple directories. You'll >have to split this into at least two components: one for the i386 directory >and one for the parent directory containing INF/CAT files. Also, you're >missing some of the files from the FTDI driver package - your list of files >is incomplete. Put the difxapp:Driver element in the parent directory >component containing the INF file. > >The same issues apply to the FTDI port section you listed below. That makes me thinking as well. Thanks! - I just wanted to copy twice all three files (.inf and .cat from root driver directory and .sys from i386 subdirectory) into the common directory and I achieved it at the beginning my tags. So, I have to deny your opinion. So when I didn't bother with installation (using difx:Driver tag, the file copied as I wanted: into FtdiBusDriver and FtdiPortDriver directores. But, I certainly think I should copy all the driver hierarchy and leave it as it is because of .inf files. I am very grateful for all your suggestions! Namely all above mentioned mestakes after using light.exe remain! -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] wix ftdi drivers
Hello,
I would
like to install two ftdi (VCP: USB to COM) drivers with WiX, among others app
stuff. I have the last WiX, i.e. v3.6. I’m bugging with it for quite some days.
I’ve read quite a lot of stuff about WiX and about drivers installation. I
haven’t checked both .inf files with ChkINF yet, but I suppose they are fine
since we use it already. I haven’t used explicit CustomAction as I saw in some
suggestions as It looks like old stuff. Well I’m using plain .wsx with
Notepad++ and command prompt candle.exe and light.exe in Win 7. I know
both drivers has to be in separate WiX components. I used difx:Driver tag as
you can see below. I have a ref in xmlns to the Difxapp extension. I used the
switches –ext in candle and light as I guessed. Maybe I’m following the wrong
path. Please, help. But as with that switch the candle compiler produce no
errors, I assume it is all right. Please, direct me to some driver installation
(two drivers even!) with WiX 3.6.
The
following is ok:
candle.exe
-ext WixDifxappExtension ftdiinstall.wsx
But after
this, I get errors:
light -ext
WixDifxappExtension ftdiinstall.wixobj
Namely:
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(29)
: error LGHT0094 : Unresolved ref
erence to
symbol 'CustomAction:MsiProcessDrivers' in section 'Product:{E00E5A99-
913D-4C68-98BF-B43A471CD45D}'.
C:\Users\hob\Documents\WiX\ftdiinstall.wsx(42)
: error LGHT0094 : Unresolved ref
erence to
symbol 'CustomAction:MsiProcessDrivers' in section 'Product:{E00E5A99-
913D-4C68-98BF-B43A471CD45D}'.
My wsx is:
