I'm working in windows 10 UWP cordova application and my client wants setup as .msi. How could I convert my .appxbundle to .msi?
Is there any proven option to create windows 10 UWP app package as .msi file?
There is no direct way to create msi file.
But you can side load your app. You can find at the end of this article
Packaging UWP apps how to sideload app package. You should run with Powershell file Add-AppDevPackage.ps1 and follow instructions.
Probably, you can create some exe file that could copy files to machine and run this script in Powershell
Related
I creating an windows forms application to configure IIS website application and also copy folder to selected location by user using visual c# 2010 express.
I want to pack the folder and application to become an executable file, like installer.
I can't find the setup template in Visual C# 2010 express.
Is there any way to pack the folder and the application to become an executable file?
One of the method that i found is use winrar. It can pack files/folder that the application needed to run into an executable file.
I am new to WUP and researching on Windows Universal platform, I have following questions for the same:
1)I would like to know if anyone has used it, and if it can be deployed anywhere else other than the windows store. How can we make the app available to the users/client without deploying it on the Windows store. (where else can we deploy the app?)
2) Will the app developed using WUP only works on Windows 10 or previous version of windows as well?
3) Can it be developed using 2015 or 2017 is mandatory?
Thanks in advance
1)How can we make the app available to the users/client without deploying it on the Windows store. (where else can we deploy the app?)
Typically, you download these apps from the Store and that is how they are installed on your device. But you can sideload apps to your device without submitting them to the Store. This lets you install them and test them out using the app package (.appx) that you have created.
For more info, please refer Sideload your app package.
We can also use the App Installer, it is a Universal Windows App that is pre-installed as part of the Windows 10 Anniversary Update. The app enables a user to double-click any .appx or .appxbundle for easy installation, eliminating the need to run PowerShell or specialized scripts.
Please refer the App Installer.
2) Will the app developed using WUP only works on Windows 10 or previous version of windows as well?
Windows 10 apps can only run on Windows 10 (and newer). If you want to target 8.1, you have to build a Windows 8.1 app. A Windows 8.1 app should run on Windows 10 without any problems.
You can refer the Develop apps for the Universal Windows Platform (UWP), it lists the requirements of UWP apps.
3) Can it be developed using 2015 or 2017 is mandatory?
Yes, we can use the VS 2015 or the VS 2017 to develop the UWP apps.
Please refer the document of Build UWP apps with Visual Studio.
I know that System.Diagnostics.Process is not available in Universal App. How do we start a locally stored .exe from an Universal App running in VS 2015?
You cannot run an arbitrary executable directly; you need to use Windows.System.Launcher to launch via registered URI scheme or file type.
We are trying to evaluate and eventually migrate to the windows azure cloud platform.
I am stumbling on the installation process...
I'm currently following this tutorial.
I can't get the Windows development Fabric interface working like on this picture.
When I install the app fabric sdk (downloaded here) I get no .exe program to simulate the cloud...
I installed Windows AppFabric which is not what I need (I think).
I keep on being directed on AppPlatformInstaller which do not install what I need but I'm sure is part of my solution.
You are downloading wrong SDK. For Windows Azure Cloud platform you must download and install Windows Azure SDK And Tools for Visual Studio.
Then you will have a folder %Program Files%\Windows Azure SDK\v1.5\bin. There will be devfabric and devstore folders, under which the local development Frabric and Development Storage executables will reside.
Then if you are targeting .NET based solutions, you will have new project templates in Visual Studio, and everything shall be running smoothly. On the other hand, if you are targeting open source solutions you might want to follow the like provided by Ben.
As for Windows AppFabric - yes, it is wrong in terms that it is not related to Windows Azure at all.
Let us know if you have any issues when downloading and installing latest Windows Azure SDK And Tools for Visual Studio
You may want to check out the docs available from the Microsoft Interoperability Team. They maintain an entire site dedicated to running PHP on Windows Azure
http://azurephp.interoperabilitybridges.com/articles/build-and-deploy-a-windows-azure-php-application
Basically to get it working just install the Windows Azure SDK and with Windows Azure SDK for PHP. Build your PHP application and then run the package command. Your PHP application will be rolled into a Windows Azure project and launched in the local dev fabric
I'm using a C# setup project which includes some pre-requisite software. These pre-req's appear to only get installed by the EXE and not the MSI (both EXE and MSI are created when I build my setup project.)
I can't always trust that my users will bother running the EXE as opposed to the MSI, so is there a way to force it? Perhaps some options:
My app needs Sql CE 3.5 SP2 - Is there a way that I can have the MSI install this instead of it only being installed in the EXE?
Is there a way to make my MSI detect when it's launched by the user instead of launched by the EXE?
Can I have my MSI launch the EXE installer as part of it's install process?
This is not supported by Visual Studio setup project. However, commercial setup authoring tools offer multiple solutions:
handle prerequisites from the MSI installation UI instead of using an EXE
embed the MSI into the EXE so you have only one setup file
configure the EXE to set a custom MSI property and create a launch condition based on that property; this way the MSI will stop if the property was not set by the EXE
If you want to continue using Visual Studio, a solution would be to create a launch condition for Sql CE 3.5 SP2. This way the installation will stop if Sql CE 3.5 SP2 is not installed.