What’s new in the MSIX PSF: Part 3 – October 2019

The Microsoft MSIX Package Support Framework (PSF) is an open source project that enables more “traditional” Win32 and Dot Net applications to be repackaged into MSIX.

As an active contributer to the GitHub project, I have added more functionality to the fixups that are available. Additionally, Microsoft has added new functionality as well. Here, I will write about the …

On Start Menu and Shortcuts

The application Start Menu Shortcut represents the most common entry point for end-users to access applications.  In this article, I’ll talk about the old shortcuts and the new, and about what happens when we repackage applications containing shortcuts into MSIX and App-V packages.  Note that this article is written in September of 2019 and we hope that improvements in support …

MSIX Code Signing Certificates Part 2 – For IT Pros

Microsoft’s replacement for the ubiquitous MSI, MSIX, requires the use of code signing certificates to deploy the packages. This is part 2 of a two-part series on MSIX and Certificates. This one is aimed at IT Pros and part 1 was for Developers.

Part 2 Introduction

IT Pros have generally not needed to really deal with code signing certificates. …

Let’s be calm again!

Yesterday I wrote a post (https://www.tmurgent.com/TmBlog/?p=2921 ) because of concerns regarding App-V and MSIX over comments made by a Microsoft employee at MMS. At the time I said “don’t panic”, and was working behind the scenes to see if we could get a public clarification over what I knew couldn’t be true.

Last night (for me here in Europe; …

App-V and MSIX today: Don’t Panic!

I’m not at MMS nor build this week. Instead I find myself in Switzerland training enterprises on how to best prepare and deploy applications using a combination of Microsoft App-V and MSIX technologies as they exist today. Yet I find myself inundated with requests for comments by enterprise customers concerned over a series of tweets from attendees at the MMS …

Short-Names and Recapture

When we capture installer activity for the purpose of creating a package to deploy on another device, the possibility of causing new issues exist. We rely on the tools that we use for the capture/packaging, the runtime environments we use on the target, and the “smarts” of the person doing the packaging to avoid these issues.

Two potential issues that …