Inno Setup is a free open-source script-driven installer creator that was released in 1997. Inno Setup has some similarities to WiX Toolset, like not having a GUI when it comes to package creation and that it's dependent on code.

Understanding custom actions can be challenging, and most beginner IT Professionals tend to “leave the chat” when custom actions are brought to the table. Without a doubt, MSI technology is complex, and best practices have evolved over the years, adding to the difficulty.

To enhance the security of your machines, it is crucial to properly define and configure the firewall rules, ensuring a safer environment.

To repackage a setup, we first need to understand how that setup was originally built. You can find a brief explanation of this in our free MSI Packaging eBook.

The Run PowerShell inline script is offered as a predefined Custom Action in Advanced Installer. This action lets you directly type a code into the Advanced Installer editor. After saving your project and building the MSI, the custom action will execute according to your configuration.

If you’ve worked with MSI Windows Installer, you most likely know that the Windows Installer database includes various interrelated tables as a standard format for component management.

Visual Studio is a powerful development tool that provides an environment for creating a wide range of applications. One of its notable features is the ability to create Setup.exe files, which greatly simplifies the deployment process for end-users.

We are excited to introduce a new Advanced Installer Visual Studio Extension improvement. Our latest update brings support for publishing .NET AOT applications directly from Visual Studio.

With VMware ThinApp, your application management and delivery across different computing environments is much easier.

Advanced installer Repackager allows you to repackage your application in multiple environments, such as the host machine, different types of virtual machines like VMware, Hyper-V, and now Windows Sandbox.

For several decades, MSI technology has played a crucial role in ensuring seamless installation of Windows Applications on a device. Typically, MSIs will only throw errors to the users if there are significant issues with the package itself.

MSIX applications can behave differently when running in an MSIX container.

Alright, let's dive into the fascinating world of portable applications!

Microsoft Office introduced add-ins, replacing the old COM plugins for developers. Now, developers create applications using Office Add-Ins, expanding the range of possibilities and features within the operating system.

Ensuring your application is well-designed is one of the key methods to keep users engaged. They need to have a positive experience while using your app, therefore a poor design can drive them away.

Cabinet files, also known as CAB files, are files that store compressed files in a file library. When it comes to Windows Installers, cabinet files can be located either inside or outside the MSI file.

We're thrilled to introduce our new feature: built-in support for repackaging in Windows Sandbox. Leverage an isolated repackaging environment without the hassle of a big virtual machine.

Even though MSI is still the preferred packaging format, there's no question that MSIX is a great complement to MSI and AppV.

Windows Forms is a UI framework used to create Windows desktop applications. This development platform provides a broad set of features to develop graphically rich and interactive applications, including a visual designer in Visual Studio.

In the previous article discussing "Repackaging vs. Wrapping", we touched upon the concept of working with wrappers in the world of software packaging and deployment.