In this customer scenario, the customer has a Windows Forms application built on .NET Framework. They are interested in “modernizing” the user interface to support touch and ink in addit...
Updated Jun 09, 2020
Version 1.0
Blog Post
A very nice post! and very timely. We started porting our current .NET Framework application to .NET Core. It will take quite a long time as we used remoting, App Domains, dynamic compilation and many more things.
One of our biggest problems at the moment is that we used ClickOnce to deploy our client software. We generated the manifest files for the deployments dynamically so that we could add configuration files that administrators can modify centrally at the server (for example with the url to the server itself ). Could this be done with MSIX? As I understand it, the MSIX packages are signed and cannot be modified later (post deployment at our customer's locations).
Or is there a way of using a MSIX package with the software itself and define a "satellite package" with files generated dynamically with configuration information (or other things).