Jack Hennessey
What's happening?
-
timeutil - Missing month of "May"
I happened to be looking at the timeutil.cpp file and noticed that the MONTH_OF_YEAR (line 22) array was missing the month of "May". So you'll never get what you expect when you call MonthFromString and pass it "May". Also, I wasn't sure how to categorize this bug...perhaps a new category like "SDK" or "dutil" should be added?.
2012-04-18 06:13:21 PDT in Windows Installer...
-
Intellisense Not Working For Some Extensions
The following files are not being installed to the Visual Studio schema location (so intellisense doesn't work for these extensions): complus.xsd lux.xsd msmq.xsd tag.xsd (this is also missing from the binaries zip file and I could find no reference to the extension in the WiX.chm file) Note that these files are correctly being installed to the "[ProgramFilesFolder]\WiX Toolset...
2012-04-18 06:04:48 PDT in Windows Installer...
-
WiX Setup v3.6.2617.0 Failure (ProjectAggregator2)
Running v3.6.2617.0 setup fails on ProjectAggregator2 (not sure if this is an issue with burn or just the WiX setup). Here is the relevant information from the log: [186A0:18E50][2012-02-20T08:39:31]: Apply begin [18B70:18C3C][2012-02-20T08:39:31]: Caching bundle from: 'C:\Users\JHENNE~1\AppData\Local\Temp\{5afb4cdc-dc2d-4505-a4f0-7835cf7f6318}\.be\WiX36.exe' to: 'C:\ProgramData\Package...
2012-02-20 06:40:20 PST in Windows Installer...
-
Comment: DownloadUrl element not fully documented.
Looks like there is a slight typo (the last '{0}' should be '{2}'). Here's what shows up in the documentation: {0} is replaced by the package Id. {1} is replaced by the payload Id. {0} is replaced by the payload file name.
2012-01-31 05:40:01 PST in Windows Installer...
-
Upgrade Leaves Files in Cache
When upgrading WiX from v3.6.2520.0 to v3.6.2527.0 the old files are left in the burn cache and not removed as expected. Log files are attached.
2012-01-30 09:14:14 PST in Windows Installer...
-
Comment: No text on WiX installer UI
hmm...still can't view it once I download it. But yeah, I realized you were talking about the WiX installer BA. Hopefully the dev team finds the information useful.
2012-01-24 13:53:05 PST in Windows Installer...
-
DownloadUrl element not fully documented.
From looking at the WiX installer source, it appears that it is valid to use some sort of formatting to construct the final URL for the *Package/@DownloadUrl attribute (I'm guessing for Payload/@DownloadUrl as well). For example the MsiPackage elements in Bundle.wxs use the value "{2}" that seems to append the name of the SourceFile to the final URL. Please document what the...
2012-01-24 13:43:58 PST in Windows Installer...
-
Comment: No text on WiX installer UI
I couldn't view your attached image (I think it's corrupt) but I suspect the problem might be the same issue I was seeing at one point with my own experimental BA. My issue was rooted in the fact that the engine performs its work (Detect, Apply, etc.) on a different thread. So, when you tell the engine to run Detect() it posts a message to the worker thread and returns immediately. In my case...
2012-01-24 11:18:05 PST in Windows Installer...
-
Comment: Add ContainsKey(string key) to Engine.Variables<T>
I noticed this at one point as well and created bug 3385047 for it. It was already fixed so you may want to get the latest version and verify.
2012-01-11 12:19:43 PST in Windows Installer...
-
Make Burn Manifest Information Accessible to BA
From discussion on the mailing list, it would be useful to be able to access the information contained in the burn manifest from a Bootstraper Application. Possible solutions would be to either include the manifest information in the BootstrapperApplicationData.xml file or to at least extract the manifest so it is available to the BA (like BootstrapperApplicationData.xml).
2012-01-11 09:54:50 PST in Windows Installer...