PSF release : version 1.0.240212.1

Framework Package support

Introducing a new remediation in RegLegacyFixup and EnvVarFixup which allows applications to get information about their dependency. In packaged environment, applications do not have write access to global registry or environment variables to share data with other applications. With this update, PSF can intercept the lookup of such information, query the information and return valid value. For more info check RegLegacyFixup README and EnvVarFixup README

Updating to this version

https://www.nuget.org/packages/Microsoft.PackageSupportFramework/1.0.240212.1

PSF release : version 1.0.231110.2

1. Deletion Marker

Introduced a new remediation in RegLeagacyFixup which allows hiding of specific registry keys or registry values in the virtual environment.. For more details refer the readme here : https://github.com/microsoft/MSIX-PackageSupportFramework/tree/master/fixups/RegLegacyFixups#deletionmarker-remediation-type

2. Error handling for mandatory files

We have now added pop-up messages (errors) for missing config.json, StartingScriptWrapper.ps1(when PowerShell script fix is applied) files inside package.

Updating to this version

https://www.nuget.org/packages/Microsoft.PackageSupportFramework/1.0.231110.2

PSF release : version 1.0.230224.1

New Features:

1. InPackageContext

InPackageContext feature provides an easy way to run dependent processes launched by an application within the same package context. This feature can be configured by setting "InPackageContext" in config.json.

2. PowerShell startScript/EndScript error handling

We have now added pop-up messages (warnings) when startScript or EndScript configured in config.json fails to run due to any reason.

Bug Fixes:

1. Powershell first launch fix in “runOnce” setting

Bug – When the "runOnce" attribute was set in config, and the PowerShell failed to run on first launch due to any reason, it did not run on a subsequent launch.
Fix – The PowerShell script will now run on every application launch until it successfully runs once.

Updating to this version

The 1.0.230224.1 package is available at https://www.nuget.org/packages/Microsoft.PackageSupportFramework/1.0.230224.1

PSF release : version 1.0.221230.1

Argument Redirection

This release includes feature that addresses an issue when the MSIX packaged application tries to open another application (say Notepad.exe) and pass on the location of the content to be consumed by it. The way some of the Win32 applications are developed, to trigger a child process, they refer native AppData path (as an argument) and was thus causing the converted MSIX to not work properly. This generalized fix, intercepts all calls from main application that triggers creation of another application, pulls out the arguments to verify the presence of referred file in per user per app data folder, if it is present, it changes the child process argument to refer it, else will not do anything. We are calling it "Argument Redirection" feature!

PSF release : version 1.0.220926.1

This release adds following new features and bug fixes:

New features:

• 'WaitForDebugger' field is introduced in config.json to debug psfLauncher for debug builds.
• Introduced new remediation type, FakeDelete, for RegLegacyFixups.
• Add new fixup : "Envinronment Variable Fixup".
• Platform upgrade from vs2017 to vs2019

Bug fixes:

• Fix in FileRedirectionFixup for PrivateProfile functions to fix the crash when null filename is passed to private profile functions.
• Not throw an error to user when shell launch returns non-zero, just Log it.
• Fixing testcases for WritePrivateProfileString and GetPrivateProfileString
• Update to documentation on PsfLauncher to mention the requirement for StartingScriptWrapper.ps1 file.
• Don't set CreationFlags when starting a process if the attributesList wasn't supplied.
• Find PowerShell.exe when system doesn't have the '1' registry key.
• Add intercept for SetWorkingDirectory
• Let DynamicLibraryFixup support dll loading with full path inputs.
• Stop FRF inception (don't redirect again if passed WritablePackageRoot).
• Fix for PsfLauncher reading incorrect case for waitForDebugger.
• Fix for redundancy check in ShouldRedirect function(in FileRedirectionFixup)
• Improving debugging during process launching in psfLauncher by adding few log information.
• Determine the bitness of the process to inject appropriate Dlls with same bitness.
• Finding StartingScriptWrapper.ps1 file in whole package directory (not just in working directory)
• Add exception handling to avoid crash when bad regex pattern is passed in config file
• Added the test ini file in the redirection pattern to fix failing test
• Fixed failing architecture tests
• Fix Powershell script failing scenarios
• Handling script arguments with space
• Updating License terms, Readme and Version details of Detours
• Added fix for consistent prefix matching for HKLM and HKCU

Removing breakout behavior

A bug caused all applications to be in the same container. This included applications that the main application launched.

For example if PSF launched Foo.exe and Foo.exe launched notepad++. Foo.exe does NOT want notepad++ to be in the container.

This release fixes that.

We also have introduced.

1. Added PriveProfile support
2. Added psuedo variable %MsixPackageRoot%, and %MsixWritablePackageRoot% for PS scripts.

Fixing breakout bahavior.

This release fixes the breakout behavior with builds done in release mode.

Binaries release

Following changes

• Powershell scripts will always run in the same environment as the package with the same permissions.
• Scripts do not run on RS1 versions of windows 10.
• New fixup: Dynamic Library Fixup. Used for when your configuration file is not in the root location.