Forum Discussion
Robert_Primorac
Nov 15, 2022Copper Contributor
MSIX update always installs in different location forcing the firewall for new rule
We want to convert our ClickOnce applications to MSIX installations but have a lot of issues. One of the issues that is plaguing us at the moment is that the application will install in different folder when updating. The location is as follows:
C:\program files\windowsapps\{app_identity}_{version}_{platfromIdentifier}_{someUniqueValue}\application\app.exe
Because of this the application will force the firewall for a new rule everytime it is updated.
This is a WPF application built in .NET 6.
I don't know what to put as additional information. I have tried so many things and now I am very much confused so if you require any additional information just ask and I will do my best to provide it.
- I believe you're only supposed to refer to the executable name, you don't want to use the full path inside your manifest since that's only consistent until you install an update (as you pointed out).
This might help: https://www.advancedinstaller.com/firewall-rules-msix.html
- WB2019Brass ContributorI believe you're only supposed to refer to the executable name, you don't want to use the full path inside your manifest since that's only consistent until you install an update (as you pointed out).
This might help: https://www.advancedinstaller.com/firewall-rules-msix.html- Robert_PrimoracCopper ContributorThanks for the reply WB2019
I have a VisualStudio generated wapproj and I hadn't touched anything in the appxmanifest so this is standard behavior.
Now that I am adding the firewal rule in the appxmanifest everything is working fine.