Skip to content

Commit

Permalink
update screen shot
Browse files Browse the repository at this point in the history
  • Loading branch information
DHancock authored Apr 15, 2023
1 parent 1a1ad0e commit 788d1fd
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,6 +14,6 @@

A typical scenario:

![application screen shot](https://user-images.githubusercontent.com/28826959/201951246-a55dd1d1-e92f-48d0-8b1a-640202f04c90.PNG)
![Screenshot 2023-04-15 174436](https://user-images.githubusercontent.com/28826959/232238992-3df0bd4d-e373-45e0-9401-142a7c3eaa0b.png)

[^1]:If not, you run the risk of ending up with orphaned framework packages that cannot be removed without reinstalling the WinAppSdk version that they were installed with. This occurs if you install a provisioned WinAppSdk, followed by a non provisioned WinAppSdk that only has a higher patch version e.g. WinAppSdk version 1.1.3 provisioned, followed by 1.1.4 non provisioned. This results in the provisioned packages having a dependency on the non provisioned framework packages. If you then attempt to remove the WinAppSdk 1.1.4 version using the utility running non elevated, both WinAppSdk versions will be removed for the current user. However if you then start the utility elevated, it appears that both WinAppSdk versions still exist. If you attempt to remove the WinAppSdk version 1.1.4 for all users, the removal fails with file not found errors. However the Package Manager still indicates that the WinAppSdk 1.1.4 framework packages remain. Further attempts to remove them also fail, sometimes without errors. Your experience may differ depending on the windows OS build.

0 comments on commit 788d1fd

Please sign in to comment.