In today’s software development industry, the partnership between PowerShell and MSI packaging continues to grow stronger.

Working with registry files is quite a simple task. However, depending on the action you want to take, you can encounter various scenarios.

Keeping your application upgraded is key for maintaining its functions and security. Regularly checking for and installing new versions ensures that your app works at its best.

With the rise of configuration files in various applications, understanding the ins and outs of INI files can elevate your productivity as a developer or software enthusiast. Despite their roots in the 16-bit Microsoft Windows platforms, INI files remain a crucial part of application configurations.

Installing software drivers can often seem like a complex task, but it doesn’t have to be. While MSI technology doesn't directly support driver installation, the Operating System (OS) provides a multitude of ways to achieve this.

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.

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.

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.

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.

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.

Object Linking and Embedding (OLE) is a proprietary technology developed by Microsoft that enables developers to embed and link to other objects.

Do you need to execute your application (exe file) as an administrator or apply compatibility options to it?

MSI is a Windows Installer package format that uses Microsoft’s Windows Installer service to manage the installation (and uninstallation) of applications.

Automation is probably one of the most used words in the IT Industry these days. We can't enter a room without hearing about it in the software packaging industry. However, sometimes simplicity is key.

If we were to manually install and manage software on a large number of target devices, the process would be very expensive and complicated. To avoid that hassle, enterprises use software deployment tools to simplify these tasks.

Windows Presentation Foundation (WPF) is a powerful User Interface (UI) framework for building desktop client apps. It's a part of .NET and offers a multitude of helpful features, such as media services, controls, data binding, and security.

In this article, we'll explore how to deploy an MSIX using Group Policies, covering Direct MSIX Deployment with Scheduled Tasks and the MSI Wrapper method.