msix

问题 I Have an Application and currently getting installed on client machine using .msi (wix Project). now I want to auto Update my application which is out of scope of wix .I am considering MSIX for this task . I Can now auto update my application . But I am not able to find a way out how to Auto start my application . In .msi application used to be installed on C: Program Files\ . But now using MSIX its in C:\Program Files\WindowsApps<Some Random ID generated by MSIX>. In .msi it was only a

来源： https://stackoverflow.com/questions/63508078/customizing-visual-studio-msix-packaging-project-output

来源： https://stackoverflow.com/questions/61020987/msix-core-solution-build-errors

来源： https://stackoverflow.com/questions/61020987/msix-core-solution-build-errors

问题 Can anyone give me a hint how I can manually define a msix package? My application has no msi package (yet), so I can’t simply convert it. Is there a way to create like a configuration file where I define manually which files need to go into the msix package? The MSIX GUI Creator doesn’t give me enough control either. Any link or help is highly appreciated 回答1: As Stein recommended, an easy way is to get the Express edition from Advanced Installer and just create an empty new project ( not

问题 We are evaluating the migration from our current client/server application to .NET Core. The 3.0 release added the support for WinForms we need for our client, but ClickOnce will not be supported. Our solution is installed on-premise and we need to include settings (among others) like the address to the application server. We create dynamically ClickOnce packages that can be used to install and update the clients and include the settings. This is working like a charm today. The users install

问题 We are evaluating the migration from our current client/server application to .NET Core. The 3.0 release added the support for WinForms we need for our client, but ClickOnce will not be supported. Our solution is installed on-premise and we need to include settings (among others) like the address to the application server. We create dynamically ClickOnce packages that can be used to install and update the clients and include the settings. This is working like a charm today. The users install

问题 I had converted msi file into msix using MSIX packaging tool. Now, how should i pass all the inputs which i used to provide/validate in msi installer screens? I had already checked the msix file for any config file to provide inputs but no such file was there. 回答1: Differences between MSIX and MSI packages , deployment wise. 1) Applying additional custom settings, like new registry or files, or modifying defaults from the original package can be done with MSIX modification packages . This is

问题 I'm trying to move to MSIX to install our application, which is currently deployed to our customers via a ClickOnce installation which requires updating on startup, if there is an update. Its a .Net Framework (4.7.2) WinForms app. I'm a bit lost on how to begin; the documentation seems to start from an existing installer package (including ClickOnce), but I'd like to generate this without an intermediate step on our build server as we want to phase out the ClickOnce installation completely

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed last year . Basically we are releasing our changes/fixes in the form of manual installer (Windows powershell script). It will install specified .dll and SQL script files at particular locations by reading config file values (We will configure .dll & Sql script locations in this file). The same powershell script has