You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm preparing to release a Windows application named uplink. I found that on windows, a folder is created next to the executable, named <application name>.exe.WebView2. This prevents me from installing the executable in the ProgramFiles directory because the exe doesn't have write access to that directory. Is there a way I can tell Dioxus to create this WebView2 folder somewhere else?
This issue is somewhat important to me because if I use the installer to uninstall the app, it won't delete the C:\uplink directory. This is because the WebView2 folder was added. If I then re-run the installer, the installer may install the new .exe because the old one is still there. In other words, if someone uninstalls uplink, downloads a installer for a different version, and runs the installer, they would still have the old version. Also, the app would look more professional if it could be installed in the ProgramFiles directory instead of whatever the LocalAppData folder happens to be (usually the last letter drive).
The text was updated successfully, but these errors were encountered:
Hello,
I'm preparing to release a Windows application named
uplink
. I found that on windows, a folder is created next to the executable, named<application name>.exe.WebView2
. This prevents me from installing the executable in theProgramFiles
directory because theexe
doesn't have write access to that directory. Is there a way I can tell Dioxus to create thisWebView2
folder somewhere else?This issue is somewhat important to me because if I use the installer to uninstall the app, it won't delete the
C:\uplink
directory. This is because theWebView2
folder was added. If I then re-run the installer, the installer may install the new.exe
because the old one is still there. In other words, if someone uninstallsuplink
, downloads a installer for a different version, and runs the installer, they would still have the old version. Also, the app would look more professional if it could be installed in theProgramFiles
directory instead of whatever theLocalAppData
folder happens to be (usually the last letter drive).The text was updated successfully, but these errors were encountered: