SOLVED

App Attach and auto update

%3CLINGO-SUB%20id%3D%22lingo-sub-1553250%22%20slang%3D%22en-US%22%3EApp%20Attach%20and%20auto%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1553250%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20Maybe%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmsix-deployment%2Fcitrix-and-xendesktop%2Fm-p%2F1521499%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fmsix-deployment%2Fcitrix-and-xendesktop%2Fm-p%2F1521499%3C%2FA%3E%20was%20too%20broad%20to%20get%20a%20response%2C%20so%20I've%20done%20some%20more%20investigation%20and%20maybe%20the%20recommended%20way%20to%20go%20with%20virtual%20desktops%2C%20Windows%20or%20Citrix%2C%20is%20with%20the%20App%20Attach%20technology.%26nbsp%3B%20Is%20the%20auto%20update%20functionality%20supported%20in%20this%20scenario%20or%20as%20an%20ISV%20does%20a%20new%20msix%20or%20vxd%20have%20to%20be%20produced%20and%20shipped%20to%20the%20client%20IT%20for%20them%20to%20add%20to%20their%20VD%20set%20up%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22yowl00_0-1596032667914.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F208810i12685118AFAF5572%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22yowl00_0-1596032667914.png%22%20alt%3D%22yowl00_0-1596032667914.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E(%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-dev-appconsult%2Fhandling-application-updates-with-app-installer-and-msix-in%2Fba-p%2F355389%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fwindows-dev-appconsult%2Fhandling-application-updates-with-app-installer-and-msix-in%2Fba-p%2F355389%3C%2FA%3E)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1564960%22%20slang%3D%22en-US%22%3ERe%3A%20App%20Attach%20and%20auto%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1564960%22%20slang%3D%22en-US%22%3E%3CP%3EI%20haven't%20tested%20this%20but%20I%20suspect%20the%20auto-update%20service%20does%20not%20apply%20to%20MSIX%20App%20Attach%20images.%20These%20images%20(and%20the%20version%20of%20the%20app%20published)%20should%20be%20controlled%20directly%20by%20the%20admins%20setting%20up%20the%20VD.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1565158%22%20slang%3D%22en-US%22%3ERe%3A%20App%20Attach%20and%20auto%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1565158%22%20slang%3D%22en-US%22%3E%3CP%3EI%20suspect%20that%20is%20the%20case.%26nbsp%3B%20It's%20not%20very%20satisfactory%20though%20from%20my%20an%20ISV%20point%20of%20view%2C%20specifically%20an%20ISV%20deploying%20on%20the%20cloud.%26nbsp%3B%20If%20you%20have%20a%20client%20server%20app%20on%20100%20clients%2C%2010%20on%20VDs%20then%2C%20and%20you%20want%20to%20perform%20an%20update%20with%20internal%20API%20changes%2C%20then%20you%20can%20do%20the%20non%20VD%20clients%20easily%2C%20but%20you%20can't%20deploy%20the%20VD%20installation's%20backends%20until%20you%20organise%20dates%20with%20the%20client%20IT%20team.%26nbsp%3B%20This%20is%20a%20worse%20workflow%20than%2C%20for%20example%2C%20a%20wholly%20cloud%20based%20deployment%2C%20e.g.%20with%20a%20web%20front%20end.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1570053%22%20slang%3D%22en-US%22%3ERe%3A%20App%20Attach%20and%20auto%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1570053%22%20slang%3D%22en-US%22%3EYou%20are%20correct%20Bogdan.%20MSIX%20app%20attach%20does%20not%20support%20auto%20update.%20Generally%20(non%20MSIX%20app%20attach%20specific)%20auto%20update%20are%20frowned%20upon%20in%20virtualized%20environments.%20Not%20saying%20this%20is%20why%20MSIX%20app%20attach%20does%20not%20support%20auto%20update%20but%20it%20falls%20in%20a%20Venn%20overlap%20between%20existing%20best%20practices%20and%20tech%20limitations.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1570587%22%20slang%3D%22en-US%22%3ERe%3A%20App%20Attach%20and%20auto%20update%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1570587%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F195573%22%20target%3D%22_blank%22%3E%40Stefan%20Georgiev%3C%2FA%3E%26nbsp%3BRight%20I%20can%20see%20that%20argument%20and%20it%20makes%20some%20sense.%26nbsp%3B%20I've%20never%20administered%20a%20VD%20setup%20but%20I%20suppose%20AppInstaller%20is%20normally%20disabled%20as%20well%20as%20it%20writes%20to%20Program%20Files%5CWindowsApps.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20a%20slight%20aside%20I%20would%20say%20the%20Venn%20diagram%20overlap%20is%20getting%20blurred%20when%20considering%20the%20differences%20between%20a%20web%20app%20and%20an%20MSIX%20app.%26nbsp%3B%20Both%20store%20the%20latest%20version%20in%20some%20kind%20of%20cache%2C%20either%20the%20browser%20cache%20or%20%25AppData%25%5CLocal%5CPackages%5C%3CGUID%3E%5CLocalCache.%26nbsp%3B%20MSIX%20runs%20with%20a%20VFS%20which%20also%20moves%20it%20more%20away%20from%20a%20traditional%20Windows%20app.%3C%2FGUID%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20things%20stand%20I%20think%20I'm%20just%20going%20to%20have%20to%20live%20with%20a%20slower%20cadence%20for%20our%20updates%20to%20VD%20customers.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi, Maybe https://techcommunity.microsoft.com/t5/msix-deployment/citrix-and-xendesktop/m-p/1521499 was too broad to get a response, so I've done some more investigation and maybe the recommended way to go with virtual desktops, Windows or Citrix, is with the App Attach technology.  Is the auto update functionality supported in this scenario or as an ISV does a new msix or vxd have to be produced and shipped to the client IT for them to add to their VD set up?

 

yowl00_0-1596032667914.png

(https://techcommunity.microsoft.com/t5/windows-dev-appconsult/handling-application-updates-with-app-...)

 

 

4 Replies

I haven't tested this but I suspect the auto-update service does not apply to MSIX App Attach images. These images (and the version of the app published) should be controlled directly by the admins setting up the VD.


I suspect that is the case.  It's not very satisfactory though from my an ISV point of view, specifically an ISV deploying on the cloud.  If you have a client server app on 100 clients, 10 on VDs then, and you want to perform an update with internal API changes, then you can do the non VD clients easily, but you can't deploy the VD installation's backends until you organise dates with the client IT team.  This is a worse workflow than, for example, a wholly cloud based deployment, e.g. with a web front end.

best response confirmed by yowl00 (Occasional Contributor)
Solution
You are correct Bogdan. MSIX app attach does not support auto update. Generally (non MSIX app attach specific) auto update are frowned upon in virtualized environments. Not saying this is why MSIX app attach does not support auto update but it falls in a Venn overlap between existing best practices and tech limitations.

@Stefan Georgiev Right I can see that argument and it makes some sense.  I've never administered a VD setup but I suppose AppInstaller is normally disabled as well as it writes to Program Files\WindowsApps.

 

As a slight aside I would say the Venn diagram overlap is getting blurred when considering the differences between a web app and an MSIX app.  Both store the latest version in some kind of cache, either the browser cache or %AppData%\Local\Packages\<guid>\LocalCache.  MSIX runs with a VFS which also moves it more away from a traditional Windows app.

 

As things stand I think I'm just going to have to live with a slower cadence for our updates to VD customers.