DotNetCore.WindowsService | Simple library | Configuration Management library

You must mark your CustomActions as Execute="Deferred"

The InstallExecuteSequence happens in two parts, the first is a planning phase where it figures out what it will be doing and the second part is running the plan script it just made in an elevated context.

If you plan some custom actions in the InstallExecuteSequence but do not mark them deferred, they will run during the planning part of the execute sequence which is before any of the files have been installed because the InstallFiles standard action requires elevation and that happens in the 2nd part of the sequence when it runs the planned script.

Generally you use this pattern when you need to run an elevated custom action that needs property values from your install. You schedule two custom actions, one deferred and one not, where the non-deferred action actually sets some special values to be used by the deferred action when it executes.

I haven't used the Directory attribute for CustomActions before so you may need to re-write some of these actions to get them to work, I'm not sure.

This other question's answer should help explain a bit how deferred custom actions get values at runtime from properties of the installer if you need to change the way your custom actions work.

WiX - commit more than one Property to deferred Custom Action

There is extension method CreateScope for IServiceProvider in Microsoft.Extensions.DependencyInjection namespace. What it does is resolve special interface (IServiceScopeFactory) from current DI container, which is responsible for creating new scopes, and creates new scope using this factory. StructureMap registers implementation of this interface, so when you call CreateScope - StructureMap will create nested container. Sample usage: