[WiX-users] wix.dll different?
for wix v3, build 3419, why is there a difference in the wix.dll that is installed with the msi and the version found in the zip file? if i install the msi to get the votive stuff and the xml references and stuff installed for VS, but then use binaries extracted into a temp directory to compile my wxs files, candle gives me an exception error, complaining about the public key token for wix.dll. if i copy the wix.dllinstalled with the MSI into my temp binary directory, it works fine. beyond compare shows the two files have the same version, but are not the same file with different file sizes and checksums. is there a reason behind this. Log file: Z:\test\wix3candle z:\test\padds\pdb.wxs -out z:\test\padds\pdb.wxs Unhandled Exception: System.IO.FileLoadException: Could not load file or assembl y 'wix, Version=3.0.3419.0, Culture=neutral, PublicKeyToken=ce35f76fcda82bad' or one of its dependencies. The located assembly's manifest definition does not ma tch the assembly reference. (Exception from HRESULT: 0x80131040) File name: 'wix, Version=3.0.3419.0, Culture=neutral, PublicKeyToken=ce35f76fcda 82bad' === Pre-bind state information === LOG: User = NYCD-7SQC691-D\dgotthar LOG: DisplayName = wix, Version=3.0.3419.0, Culture=neutral, PublicKeyToken=ce35 f76fcda82bad (Fully-specified) LOG: Appbase = file:///Z:/test/wix3/ LOG: Initial PrivatePath = NULL Calling assembly : candle, Version=3.0.3419.0, Culture=neutral, PublicKeyToken=c e35f76fcda82bad. === LOG: This bind starts in default load context. LOG: Using application configuration file: Z:\test\wix3\candle.exe.Config LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework\v2 .0.50727\config\machine.config. LOG: Post-policy reference: wix, Version=3.0.3419.0, Culture=neutral, PublicKeyT oken=ce35f76fcda82bad LOG: Attempting download of new URL file:///Z:/test/wix3/wix.DLL. WRN: Comparing the assembly name resulted in the mismatch: PUBLIC KEY TOKEN ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixShellExec CAQuietExec their options
that is exactly what i assumed about the process creation and exactly what i was going to try. at least i know i wasn't so far off. is there any way in the future that maybe the ability could be added to the CAQuiateExec function which will read another property that could be set to specify working directories? It could be a constant property name for all CAQuietExec functions, like CAQuietDir or something? On 8/24/07, Schrieken, Rene [EMAIL PROTECTED] wrote: The CreateProcessW is called with NULL as its currentdirectory parameter. From the win32 sdk: If this parameter is NULL, the new process will have the same current drive and directory as the calling process As msiexec is in system32... I'm not sure if this might work: make your commandline for qtexec like this: [System32]\cmd.exe /c start /D[INSTALLDIR] [INSTALLDIR]Yourapp.exe That should start a new cmd processor, and execute the start command which has the option /D to specifiy the current dir. Rene -- *From:* [EMAIL PROTECTED] on behalf of koawmfot *Sent:* Thu 8/23/2007 21:55 *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] WixShellExec CAQuietExec their options I need to lauch an executable at the end of my installation. currently i use the CAQuietExec function and launch the executable with its parameters and it is fine. the problem is that the command i execute creates a result text file. the file is supposed to be created in the application's INSTALLDIR (and is created there when the app is launched through its shortcut). instead, the text file is created in the system32 directory. so my question is, is there any way to specify a working directory for CAQuietExec function? what options do i have for the WixShelExec since i need this to be a silent install and cannot use an immediate CA since there will be no UI? This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] WixShellExec CAQuietExec their options
that is exactly what i assumed about the process creation and exactly what i was going to try. at least i know i wasn't so far off. is there any way in the future that maybe the ability could be added to the CAQuiateExec function which will read another property that could be set to specify working directories? It could be a constant property name for all CAQuietExec functions, like CAQuietDir or something? On 8/24/07, Schrieken, Rene [EMAIL PROTECTED] wrote: The CreateProcessW is called with NULL as its currentdirectory parameter. From the win32 sdk: If this parameter is NULL, the new process will have the same current drive and directory as the calling process As msiexec is in system32... I'm not sure if this might work: make your commandline for qtexec like this: [System32]\cmd.exe /c start /D[INSTALLDIR] [INSTALLDIR]Yourapp.exe That should start a new cmd processor, and execute the start command which has the option /D to specifiy the current dir. Rene -- *From:* [EMAIL PROTECTED] on behalf of koawmfot *Sent:* Thu 8/23/2007 21:55 *To:* wix-users@lists.sourceforge.net *Subject:* [WiX-users] WixShellExec CAQuietExec their options I need to lauch an executable at the end of my installation. currently i use the CAQuietExec function and launch the executable with its parameters and it is fine. the problem is that the command i execute creates a result text file. the file is supposed to be created in the application's INSTALLDIR (and is created there when the app is launched through its shortcut). instead, the text file is created in the system32 directory. so my question is, is there any way to specify a working directory for CAQuietExec function? what options do i have for the WixShelExec since i need this to be a silent install and cannot use an immediate CA since there will be no UI? This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you. - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] WixShellExec CAQuietExec their options
I need to lauch an executable at the end of my installation. currently i use the CAQuietExec function and launch the executable with its parameters and it is fine. the problem is that the command i execute creates a result text file. the file is supposed to be created in the application's INSTALLDIR (and is created there when the app is launched through its shortcut). instead, the text file is created in the system32 directory. so my question is, is there any way to specify a working directory for CAQuietExec function? what options do i have for the WixShelExec since i need this to be a silent install and cannot use an immediate CA since there will be no UI? - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] heat switches, and other exe's
searching around i found that the -gg switch when passed to heat generates
GUIDs for each component. this is a very nice little feature, and i wonder
why it is undocumented with the /?.
i was wondering if there are other undocumented switches for heat, as well
as undocumented switches for the other wix tools.
also, specifically with heat, i would like to be able to not seperate every
componet into a fragment. when capturing large directories, it is very
tedious to add every component created to a feature, and it is not possible
to create a componentgroup when every component is in a seperate fragment.
at the same time, i was wondering if the DirectoryRef that is created for
each component could be moved to be a directory attribut of the component
elements created.
in other words, instead of this:
Fragment
DirectoryRef Id=bicarboc
Component Id=a2_2_11.cxf
Guid={192F8473-F096-466E-A54C-DD748E31ADA2}
File Id=a2_2_11.cxf Name=a2_2_11.cxf KeyPath=yes
Source=c:\sf\templatedirs\bicarboc\a2_2_11.cxf /
/Component
/DirectoryRef
/Fragment
Fragment
DirectoryRef Id=coordina
Component Id=a5member.cxf
Guid={5314AA6A-1F30-440B-B0EF-AA274E88ACD6}
File Id=a5member.cxf Name=a5member.cxf KeyPath=yes
Source=c:\sf\templatedirs\coordina\a5member.cxf /
/Component
/DirectoryRef
/Fragment
Fragment
DirectoryRef Id=polycarb
Component Id=ab3_1_0.cxf
Guid={45FB27BE-A664-4035-B00B-30AD8E8F2658}
File Id=ab3_1_0.cxf Name=ab3_1_0.cxf KeyPath=yes
Source=c:\sf\templatedirs\polycarb\ab3_1_0.cxf /
/Component
/DirectoryRef
/Fragment
I was wondering if there were any switches for heat that would give me this
instead:
Fragment
Component Id=a2_2_11.cxf
Guid={192F8473-F096-466E-A54C-DD748E31ADA2} Directory=bicarboc
File Id=a2_2_11.cxf Name=a2_2_11.cxf KeyPath=yes
Source=c:\sf\templatedirs\bicarboc\a2_2_11.cxf /
/Component
Component Id=a5member.cxf
Guid={5314AA6A-1F30-440B-B0EF-AA274E88ACD6} Directory=coordina
File Id=a5member.cxf Name=a5member.cxf KeyPath=yes
Source=c:\sf\templatedirs\coordina\a5member.cxf /
/Component
Component Id=ab3_1_0.cxf
Guid={45FB27BE-A664-4035-B00B-30AD8E8F2658} Directory=polycarb
File Id=ab3_1_0.cxf Name=ab3_1_0.cxf KeyPath=yes
Source=c:\sf\templatedirs\polycarb\ab3_1_0.cxf /
/Component
/Fragment
thanks
doug
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/___
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] advertising extensions
i am not sure what doc you are reffering to, maybe the help document?
anyway, i found another problem, but this one lets the msi actually install
and seems to bury a 2228 error, and is also easy to replicate as well.
what happens now is that i added a progid element above my extension
element, and added a verb element underneath it. (note, there are no
advertised classes anywhere in my installation, therefore no table is
created in the compiled msi.) this is the code snippet:
Component Id='player.exe' Guid='{GUIID}' Directory='player'
File Id='player.exe' Name='player.exe' KeyPath='yes' Source='.\program
files\player\player.exe' /
ProgId Id='RM.3gp' Description='Video File' Icon='IconP.ico'
IconIndex='1' Advertise='yes'
Extension Id='3gp' Advertise='yes'
MIME Class='{CFCDAA03-8BE4-11CF-B84B-0020AFBBCCFA}'
ContentType='video/3gpp' Default='yes' /
Verb Id='open' Argument='quot;%1quot;' Command='Play' /
/Extension
/ProgId
/Component
it compiles and validates perfectly fine. the installation even installs
without error. the problem now is that the progid i am creating does not
get the description or the default icon. the verb table values go in
correctly, but not the progid stuff. looking at the log file, i see this:
MSI (s) (6C:38) [14:26:07:953]: Doing action: RegisterProgIdInfo
Action ended 14:26:07: RegisterExtensionInfo. Return value 1.
MSI (s) (6C:38) [14:26:07:953]: Note: 1: 2205 2: 3: Class
MSI (s) (6C:38) [14:26:07:953]: Note: 1: 2228 2: 3: Class 4: SELECT
DISTINCT `BinaryType`, `ProgId`, `Class_`, `ProgId`.`Description`,
`ProgId`.`Icon_`, `ProgId`.`IconIndex`, null, `Component`.`RuntimeFlags`,
`Component`.`Component` FROM `ProgId`, `Class`, `Feature`, `Component` WHERE
`ProgId`.`Class_` = `Class`.`CLSID` AND `Class`.`Feature_` = `Feature` AND
`Class`.`Component_` = `Component` AND ((`Feature`.`Action` = 1 OR
`Feature`.`Action` = 2) OR (`Feature`.`Action` = 4 AND
`Feature`.`Installed` = 0) OR (`Feature`.`Action` = 3 AND
(`Feature`.`Installed` = 1 OR `Feature`.`Installed` = 2 OR
`Feature`.`Installed` = 4)) OR (`Feature`.`Action` = NULL AND
(`Component`.`Action` = 1 OR `Component`.`Action` = 2) AND
((`Feature`.`Installed` = 1 OR `Feature`.`Installed` = 2 OR
`Feature`.`Installed` = 4
Action start 14:26:07: RegisterProgIdInfo.
MSI (s) (6C:38) [14:26:07:953]: Doing action: RegisterMIMEInfo
Action ended 14:26:07: RegisterProgIdInfo. Return value 0.
the return value tells me there is something wrong, and so i add an empty
class table (since the two about notes seems to be metioning something is
wrong with it) using orca this time, and now the installation is fine. the
log now reads like this.
MSI (s) (6C:24) [14:32:14:078]: Doing action: RegisterProgIdInfo
Action ended 14:32:14: RegisterExtensionInfo. Return value 1.
MSI (s) (6C:24) [14:32:14:078]: Note: 1: 2262 2: Class 3: -2147287038
Action start 14:32:14: RegisterProgIdInfo.
MSI (s) (6C:24) [14:32:14:078]: Doing action: RegisterMIMEInfo
Action ended 14:32:14: RegisterProgIdInfo. Return value 1.
the error 2262 i am guessing is because there is no info in the class table
that the progid points to, but this is not fatal and the results (or the
final installation) is ok.
i guess i am wondering why if the extension table is dependent on the verb
table (from the first post), and the progid table seems to be dependent on
the class table, why then are they not included during a compile, even if
they do not need to contain any data? why does this not seem to be
documented anywhere? it took me the entire day so far (6 hours) to figure
out why the progid description and default icon were not coming up and could
not find any documentation anywhere that helped or specified that you need
this table, albeit empty, jsut to exist for the registration of the other
tables to occur correctly. let me know if i am off the wall on this one.
also, would this be two bugs or one if i were to file, and is this a bug in
the documentation, or the compiler?
thanks
doug
On 7/28/07, Bob Arnson [EMAIL PROTECTED] wrote:
koawmfot wrote:
i need to advertise a ffew file extensions so that self repair can
kick off for some specific HKCU registry keys. the problem i have is
that i am only adding an extension element and a MIME element, but no
verb element, and that leaves the verb table out of the final MSI.
now if i try and install the MSI, it dies registering the extension,
with error 2228. if i add an empty verb table using orca, the
installation is fine. in other words, it needs to see a verb table,
but doesn't need it to have any data in it.
shouldn't this table then be by light.exe once it is detected that the
extension element is advertised? maybe light.exe needs to be
updated? or maybe i am doing something completely wrong?
The doc seems pretty clear, so please enter a bug. If you can include a
small sample that shows the problem, that'd be helpful.
--
sig://boB
http
[WiX-users] advertising extensions
i need to advertise a ffew file extensions so that self repair can kick off for some specific HKCU registry keys. the problem i have is that i am only adding an extension element and a MIME element, but no verb element, and that leaves the verb table out of the final MSI. now if i try and install the MSI, it dies registering the extension, with error 2228. if i add an empty verb table using orca, the installation is fine. in other words, it needs to see a verb table, but doesn't need it to have any data in it. shouldn't this table then be by light.exe once it is detected that the extension element is advertised? maybe light.exe needs to be updated? or maybe i am doing something completely wrong? thanks doug - This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now http://get.splunk.com/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] jet 4.0 msm's
microsoft provides an msm for MDAC, and the instructions on how to update it, here: http://support.microsoft.com/kb/320788. i atcually used that, and converted to a wixlib, and was hoping to do the same for JET. i was wondering if anyone had anything similar for JET 4.0 SP8. i know there are wise and installshield msm's for jet 4 sp8, but i'd rather stick to something from MS or configure my own. has anyone come up with a solution? thanks doug - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] QTExec and WixUtilExtension
The infor below was posted on the mail list: Re: [WiX-users] WiX 3.0 wixca.dll QtExec Erlichmen, Shay Wed, 21 Feb 2007 03:51:59 -0800 There is a documentation mistake in WiX3 chm, you need to replace the Id=wixca with Id=WixCA and remove the Binary element. Then you will need to add WixUtilExtension to light using -ext switch. Property Id=QtExecCmdLine Value=command line to run/ CustomAction Id=QtExec BinaryKey=WixCA DllEntry=CAQuietExec Execute=immediate Return=check/ . . . InstallExecuteSequence Custom Action=QtExec After=TheActionYouWantItAfter/ /InstallExecuteSequence The problem i am having is that i am getting this error becusei am no longer including the binary. c:\test\app\unify\unify.wxs(150) : error LGHT0094 : Unresolved reference to symbol 'Binary:wixca' in section Fragment:unify_drivers'. now i know that is because i no longer am including wixca.dll in the binary table. if the CAQuietExec function is now included in WixUtilExtension, what is the proper code then to make the call? doug - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
[WiX-users] problem with serviceconfig
using v3.0.2911.0 i had no problem with the WixUtilExtension and ServiceConfig element. I just installed v3.0.3001.0 and now my msi dies when it gets to SchedServiceConfig. below is the relevent MSI log file information: Action start 13:26:37: SchedServiceConfig. MSI (s) (10!38) [13:26:37:715]: Doing action: RollbackServiceConfig Action start 13:26:37: RollbackServiceConfig. Action ended 13:26:37: RollbackServiceConfig. Return value 0. SchedServiceConfig: Error 0x8007065a: Failed MsiDoAction on deferred action SchedServiceConfig: Error 0x8007065a: failed to schedule RollbackServiceConfig action MSI (s) (10:EC) [13:26:37:715]: Machine policy value 'DisableRollback' is 0 MSI (s) (10:EC) [13:26:37:715]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 Action ended 13:26:37: SchedServiceConfig. Return value 3. I tried the different versions and recompiling the same code with any version from v3.0.2921 and higher does not work. Was something changed in the newer version of WixUtilExtension.dll that broke it? thanks doug - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wixlib and extensions and msm's
thanks for your help bob... On 5/2/07, Bob Arnson [EMAIL PROTECTED] wrote: Light is a smart linker; it links in only the sections that are referenced. A section is a Product, Module, or Fragment (and probably Patch and PatchCreation, just to be pedantic). You can break up your authoring however you want, because a Wix element can have multiple Fragment children. So just break up your control authoring into multiple Fragments and only the authoring in each fragment will get linked in. thanks... worked perfectly. i wasn't aware that referencing a component in a fragment pulled in the whole fragment. took 2 seconds to fix and we are golden. I wouldn't be at all surprised if WiX didn't explicitly support Win16 -- I mean, it is 2007, you know.g If you look in src\wix\Compiler.cs for ParseTypeLibElement, you'll see that it mentions Win16 in a comment only to ignore it in favor of win32/win64 based on the component attribute. I realize it is 2007, the problem is that some third party developers are stuck in 1995. I don't think it exists, so feel free to enter a feature request. I'm not sure how to make it fit together with the Win64 attribute, so it's not necessarily straightforward. maybe if i get another app to repackage that still is frozen in time, but for now i'll let it pass. 4. And finally, when compiling, the Class element InprocServer(32) values are entered into the registry table with quotation marks (i.e. C:\windows\system32\mscomctl.ocx) and when the control is manually registered to verify the msi entries, the quotation marks are removed from the entries. Is this an incorrect design? Which version of WiX are you using? I believe that was changed sometime recently to not quote. I am using v3.00.2813. i believe that is the last release. thanks again. doug - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wixlib and extensions and msm's
PROTECTED] wrote: koawmfot wrote: Which version of WiX are you using? I believe that was changed sometime recently to not quote. I am using v3.00.2813. i believe that is the last release. Hmmm...Can you post the WiX authoring and the resulting Registry rows? -- sig://boBhttp://joyofsetup.com/ - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wixlib and extensions and msm's
ok.. perfect answer and that is what i thought... so that set me on my path and leaves me know with a few other questions, one related to the topic and a few slightly off-topic... i am using only wix v3. 1. I have authored a large file containing maybe 50 vbcontrols (ocx, dll) and compiled it into a master binary wixlib containing the files. My goal was to reference components from this master file when i needed specific ones in a main project. The problem is that it includes all of the components, and the ones that are not referenced in features are orphaned in the final msi. The question is then: Do I need to separate the components into separate wixlib files or am i doing something wrong in the referencing? i will gladly provide the source code upon request if it would help answer. 2. I have a few 16-bit register-able controls. I am not advertising the registry information but I am using the typelib/class/progid elements in the wxs file for format and consistency. Also, heat captured the registry information into these elements as well. The problem i have is that when the msi is compiled, it creates a win32 entry for the type library info instead of the win16 entry it should be. Then question is then, is the only way to get the correct info to use the actual registry elements instead of the typelib element? Would it be possible to maybe include an attribute for the typelib element, similar to the win64 attribute for the component element, called maybe 'winversion' or something, and the allowed values are 16, 32, and 64?? Or does this ability exist and i am missing it? it is overwriting the corresponding 32-bit controls win32 value, and i'd like to be able to specify win16 somehow and still use the typelib element. 3. An expansion on question 2. When wxs is compiled to the msi, how is it determined what the FLAGS value for the typelib element will end up becoming? 4. And finally, when compiling, the Class element InprocServer(32) values are entered into the registry table with quotation marks (i.e. C:\windows\system32\mscomctl.ocx) and when the control is manually registered to verify the msi entries, the quotation marks are removed from the entries. Is this an incorrect design? So if you read this far, thanks for your time, and if anyone wants, they can seperate these into different answers. Thanks doug On 4/7/07, Bob Arnson [EMAIL PROTECTED] wrote: koawmfot wrote: well, technically it isn't really a bug if the v2 difxapp.wixlib has different elements and schema references than it should in v3. True -- I'm not saying it'll get fixed.g WiX v3 added the concept of binary .wixlibs that can contain the files they ship, so they're full replacements for merge modules. it is really just not an ap to date wixlib. unless what you are saying is that the WixDifxAppExtension.dll contains the v2 wixlib and that is why i need to provided an 'altered' version wixlib with v3 elements and references as well as the extension which provided the shema? The v3 extension doesn't include the .wixlib which is why it starts working when you include the altered one on the light command line. what is the final method going to be? only an extension? (i would assume...) Yes, with a v3 embedded .wixlib. -- sig://boB http://bobs.org - This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
Re: [WiX-users] wixlib and extensions and msm's
well, technically it isn't really a bug if the v2 difxapp.wixlib has different elements and schema references than it should in v3. it is really just not an ap to date wixlib. unless what you are saying is that the WixDifxAppExtension.dll contains the v2 wixlib and that is why i need to provided an 'altered' version wixlib with v3 elements and references as well as the extension which provided the shema? what is the final method going to be? only an extension? (i would assume...) On 4/6/07, Bob Arnson [EMAIL PROTECTED] wrote: Correct -- DifxApp itself doesn't ship with WiX v3. There's an open bug right now that WiX v3 can't consume the WiX v2 Difx .wixlib. -- sig://boB http://bobs.org - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV___ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
