Forum Discussion
MSIX Pakage for Testing then Production
Hi SteveDeleon
Sorry, but I don't follow. What is the difference between the prod and non-prod environments?
I am trying to understand why do you think there is a limitation. Different VS configs?
Bogdan Mitrache Thanks for the response.
I'm new to APPX/MSIX so it may be a simple thing, I just have the assumption that if an MSIX package is updated on an internal network share for internally developed apps, all client machines that have that app installed would get updated. Just trying to see how we can only deploy to testers then to all users without having to change the package .... perhaps configs, policies, etc. ?
To answer your question, the difference between prod and non-prod is it depends on the dev team and how they implemented but in summary it can be how the app is installed and/or launched (e.g. install location/package may be different, maybe params passed in via shortcut; env=dev, env=qa, env=prod, etc.). I am just starting to look at AppX/MSIX for our internal apps and just want to see how it would fit into our current process and maybe standardize across the board with MSIX 🙂
Hopefully that makes sense.
Thanks,
Steve