Including PPLs using the slnfile method results in the PPLs being swapped in alphabetical order (due to them being stored in a set), but the order of replacement was significant in my testing.
I found that if I replaced the PPLs in the order they were created in, the build succeeded, but the build failed if I attempted to replace alphabetically.
Can a feature be added to programmatically determine the dependency order of previously created PPLs?
Including PPLs using the slnfile method results in the PPLs being swapped in alphabetical order (due to them being stored in a set), but the order of replacement was significant in my testing.
I found that if I replaced the PPLs in the order they were created in, the build succeeded, but the build failed if I attempted to replace alphabetically.
Can a feature be added to programmatically determine the dependency order of previously created PPLs?