Replies: 1 comment
-
Added a #5 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I have the following v3 code that compiles and works:
I then use heatwave/wixcop to convert to v4 and that's where I start to have issues and questions.
error WIX0033: Breaking change: util:RegistrySearch for a value no longer clears the variable when the key or value is missing. See the conversion FAQ for more information: https://wixtoolset.org/docs/fourthree/faqs/#converting-bundles (UtilRegistryValueSearchBehaviorChange) --- I read the FAQ and I didn't really absorb anything on what I should do if anything. This doesn't seem to be a compile break post install either so should it be a warning?
When I try to compile I get: WIX0035 The ExePackagePayload/@hash attribute cannot be specified when attribute CertificatePublicKey is present. - Should WiXCop have caught this? I also read that it's SHA512 now instead of SHA1 so it seems like this should have been another error/warning and possibly nulling out the value so it's no longer valid. Regardless, I remove the attribute to proceed.
The wixlib now builds successfully so I go ahead and create a bundle project to consume it. The bundle build fails with WIX0010 The ExePackage/@cacheid attribute was not found; it is required when attribute CertificatePublicKey is specified. That's strange... shouldn't the wixlib failed to have built for the same reason? I go ahead and add
CacheId="test"
and it all builds.Now I go to upate this fragment from 6.0.2 to 6.0.22. I get the URL, download the file and find
wix burn remotepayload
. I see that it says certificate validation is not reccomended but I try it anyways since I've had experiences in the past where Microsoft decided to re-release something to the same URL. In this scenario the hash check failed but the cert check worked. Since, as stupid as that is, that's what they intended... I went with it. Since the size and version could change I decide to remove those attributes. Again the wixlib builds but the bundle fails with: WIX0001 System.InvalidOperationException: Nullable object must have a value. This error goes away when I put version back in.I ditched the RegistrySearch and moved on to netfx:DotNetCoreSearch. When I first tested I got this error: . Error 0x800700c1: Failed to load BundleExtension DLL 'Wix4NetfxBundleExtension_X86' It seems to be because I built my wixlib as x86 and my bundle as x64. When I rebuilt the wixlib as x64 the problem went away. But is this correct? It seems like the wixlib should be platform independent so that whoever consumes it will set the bitness.
I atleast one issue to file here.. but maybe a few more. What say you all?
Beta Was this translation helpful? Give feedback.
All reactions