Message136418
I wasn't so happy trawling through \windows\installer either :)
Creating an MSI to test is very simple, and actually quicker than I had originally thought. The latest patch (support_dir_for_msi_objs.patch) creates the one and just uses that. Optionally I could create a new one each time setUp()/tearDown(). But was thinking - let's do that if/when we need to :)
The latest patch updates the tests - but no change to the C code.
(I doubt the error you received is a bug in msilib, and I couldn't repro even by opening EVERY MSI in my windows\installer dir. It could be a rights/security issue? The previous test was not opening as READ ONLY - even though it never saved the db, so that may be another reason?) |
|
Date |
User |
Action |
Args |
2011-05-21 01:01:57 | markm | set | recipients:
+ markm, loewis, amaury.forgeotdarc, brian.curtin |
2011-05-21 01:01:57 | markm | set | messageid: <1305939717.11.0.535332588646.issue11702@psf.upfronthosting.co.za> |
2011-05-21 01:01:56 | markm | link | issue11702 messages |
2011-05-21 01:01:56 | markm | create | |
|