Actually i created MSI package for WCF service using Advance Installer.
Now i want to create MSI or exe package for WCF service Using *INNO SETUP*
I am using Inno Script Studio 5.5.3.
I am beginner in Inno setup, now only i installed the Inno setup application,So i don't aware of anything.
I am having dll which is created with the help of WCF service.Then I created window service application with reference of dll, then created exe package with service application.
How can i create MSI or exe package using INNO setup.
It is possible to create setup with the help of WCF service dll alone.
Else if i need to use exe of windows service application, to create msi or exe package for INNO Setup .How it is possible?
Please give me some sample application (or) steps to proceed for INNO setup..
Regards,
Lokesh.J
If you'd follow this post, the InnoSetup script for installing such service might look like this (just copy and paste it into the InnoSetup code editor and save it somewhere on your harddrive):
[Setup]
AppName=App Name
AppVersion=1.5
DefaultDirName={pf}\Folder Name
[Files]
Source: "C:\SomeFolder\YourService.exe"; DestDir: "{app}"
[Run]
Filename: "{app}\YourService.exe"; Parameters: "--install"
[UninstallRun]
Filename: "{app}\YourService.exe"; Parameters: "--uninstall"
Related
I want to create installer that will install my ASP.Net Core 3.1 app as windows service (the app code already has .UseWindowsService();).
Right now when i publish the app, there are a lot of files and i just use sc create command in cmd to install it as service (specifying .exe path).
I want to create just one exe file that will include installer and files needed for installation. I would like to have some basic ui where you could choose path if you want different path than default. It should start service after installation and set it to start automatically. Before installation it should check if service is already installed and if it is, try to start it and inform user about it.
The located at https://github.com/iswix-llc/iswix-tutorials will handle this. Build your EXE to not require .net core. If you want to install .net core as a prereq instead you'll want to use the IsWiX bootstrapper project template and add .net core to your bundle.wxs.
This short video shows the whole process that's described in the tutorial.
https://www.youtube.com/watch?v=bxbcPnjfzIc
Hi We have a scenario here:
We deployed DLLs in the system through setup installer.
Now we upgraded the DLLs and created msm file for that.
Now want to deploy the upgraded DLL through patch/hotfix installer instead of setup installer.
How to do this?
Basically you rebuild the MSI file with the new merge module and then use that against the original MSI file to create a patch. It's the same as if the file was not in a merge module - you still increment its file version, rebuild the MSI and then create a patch. The Windows SDK method would be to use MsiMsp.exe and a .PCP file with options and references to the old and new MSI administrative images. This should help:
http://trentm.com/2007/05/building-msi-patch-packages-msp-with-wix.html
WiX can do patching too,
http://wixtoolset.org/documentation/manual/v3/patching/wix_patching.html
I'm very new to WiX based applications, and I need to create an MSI file where it has to check for .NET Framework 4.0 and SQL Server 2008. If they are not installed, I have to get them installed first and then have to install my application's EXE file and one more VBScript agent. It must be done like when you install WiX 3.7 setup (if we double click the setup file, it will show a UI as shown below!
Where do I start? Is there any step-by-step guide to develop this kind of application?
You'll need the following projects. They can be created from project templates in Visual Studio. Each of them would probably have separate tutorials that you might find with a Web search.
A WiX Setup project to build an .msi. The source files for such a project declare a WiX/Product. It could have conditions that check for .Net Framework4.0 and SQL Server 2008. If a check fails, installation of the .msi will fail, which is all that can be done in an .msi. The project would include your application .exe as a Component.
A WiX Bootstrapper project to build an .exe. The source files for such a project declare a WiX/Bundle. In the bundle is a Chain of installers, which would include .Net Framework4.0, SQL Server 2008, your .msi, and your VBScript Agent.
A WPF Library project to provide a BootstrapperApplication implementation with a custom UI for the bootstrapper project.
Your best bet is to consult the documentation, the WiX source code and various tutorials. Keep in the mind that tutorials might be out-of-date--in most cases WiX has gotten simpler with each version.
I need to distribute my WPF application. I am using WIX for building the Setup.exe.
But I also need to ensure that the .net framework 4.0 is first installed on the user's PC. I have downloaded dotNetFx40_Full_x86_x64.exe but how do I create a WIX installation that will contain MyApp.Msi and the .net framework redistribution file?
What I really want is to have just 1 Setup.exe that contains and runs both installs(my.msi and the .exe) in order.
Can this be done with WIX? Is there a better solution?
You can use the WiX bootstrapper technology (referred to as Burn) to create a single bootstrapper to install .NET and your .msi. Burn will enable you to embed the .NET redistributable and your .msi into a single setup.exe as well.
A setup bootstrapper is the file that could install the .NET framework. You can read about the WiX bootstrapper here. If you want the final output to be one .EXE file, you can pack the bootstrapper and the .MSI file into a new .EXE file using IExpress. IExpress is included in your Windows installation.
With WiX + IExpress you can create an installation package contained in one .EXE file.
I have created a bootstrpper using the dotNetInstaller tool. The created bootstrapper internally has these installers:
.NET Framework 4.0
SQL Server Express
Now through WiX, what are the steps that I need to follow to invoke the above Bootstrapper from WiX?
You should not invoke a bootstrapper from WiX - that has no sense. The idea behind the bootstrapper is to "bootstrap" the prerequisites of the installation (.NET and SQL Express in your case) and the main installation package. The main package you generate with WiX should be launched from inside the bootstrapper when the prerequisites are checked and optionally installed.
See this article for better understanding how to start with bootstrapper authoring with WiX.
If you are using WiX to create installers, I would suggest using WiX to create your bootstrapper as well.
http://wix.sourceforge.net/manual-wix3/authoring_bundle_intro.htm
You can only invoke packages from using bootstrapper, you can't invoke it from WiX. By the use of dotNetInstaller you can easily invoke one after another. One of the process as #Yan introduced. By the help of prerequisites folder. It is a very efficient and popular process. But what can I suggest for you, invoke link instead of folder. So your installation full package wouldn't not so bulky. Whatever the msi need it can directly download from internet and install it one after another. Follow the link.
http://www.codeproject.com/Articles/5116/dotNetInstaller-Setup-Bootstrapper-for-NET-Applica