With the recent changes to hostfxr/hostpolicy dotnet/core-setup#5859 which added the new native hosting capabilities, there are relatively large differences in behavior when hostfxr runs against new hostpolicy and when it runs against the old hostpolicy. We don't have good coverage for the latter case.
Similarly we need to add coverage for testing old apphost against the new hostfxr. Although this might be basically a no-op.
It's impractical to add true real-world tests for these (we should rely on app compat testing for that). Instead we should add tests which validate that hostfxr behaves correctly when given hostpolicy (mock) which looks like the old one.
Similarly we should be able to test apphost against a mock hostfxr which looks like the old one and vice versa.
With the recent changes to
hostfxr/hostpolicydotnet/core-setup#5859 which added the new native hosting capabilities, there are relatively large differences in behavior whenhostfxrruns against newhostpolicyand when it runs against the oldhostpolicy. We don't have good coverage for the latter case.Similarly we need to add coverage for testing old
apphostagainst the newhostfxr. Although this might be basically a no-op.It's impractical to add true real-world tests for these (we should rely on app compat testing for that). Instead we should add tests which validate that
hostfxrbehaves correctly when givenhostpolicy(mock) which looks like the old one.Similarly we should be able to test
apphostagainst a mockhostfxrwhich looks like the old one and vice versa.