MicrosoftEdge / MicrosoftEdge/WebView2Samples
Changing content under Evergreen Bootstrapper link
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1k
- Forks
- 521
- Avg merge
- 13m
- Merged PRs (30d)
- 1
Description
Hi devs,
I tried the sample under SampleApps/WV2DeploymentWiXBurnBundleSample/Bundle.wxs. It contains the following part:
<ExePackage
Id="DownloadAndInvokeBootstrapper"
Name="Install WebView2 Runtime"
Cache="no"
Compressed="no"
PerMachine="yes"
Vital="no"
DownloadUrl="https://go.microsoft.com/fwlink/p/?LinkId=2124703"
InstallCommand=" /silent /install"
InstallCondition="NOT (REMOVE OR WVRTInstalled)">
<RemotePayload
ProductName="MicrosoftEdgeWebview2Setup"
Description="Microsoft Edge WebView2 Update Setup"
CertificatePublicKey="1392A8505C3B192F62311EA9005E49C1B5358F6B"
Hash="82B42348804E8D82C773DC3391B691712BB1B388"
Size="1815832"
Version="1.3.135.41"/>
</ExePackage>
But under the given link https://go.microsoft.com/fwlink/p/?LinkId=2124703 I get a bootstrapper of version 1.3.167.21 with another file size and - of course - another hash. For that reason I am not able to check the file integrity, because the file is changing.
Is this wanted?
Best regards,
Georg
PS: I guess it's the same issue as #65
PPS: Relates to my issue at WebView2Feedback.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with SampleApps/WV2DeploymentWiXBurnBundleSample/Bundle.wxs and compare its RemotePayload values with the bootstrapper currently returned by the DownloadUrl. Read the related discussion in #65 and the linked WebView2Feedback issue to determine whether the changing download is expected. Done means the sample's integrity metadata or its documented behavior matches the current download process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100