Remove BundleLegacy test targeting netcoreapp3.0/3.1 #94118
Conversation
|
Tagging subscribers to this area: @agocke, @vitek-karas, @VSadov Issue DetailsThese were building a self-contained app targeting netcoreapp3.0/3.1 and then running the single-file bundler on everything in the self-contained publish output directory. With 3.1 having been out of support for nearly a year, I don't think they add much value. We have other tests that target the extraction behaviour via bundler options.
|
|
I'm a bit undecided on this - while 3.1 is out of support, technically SDK still supports building 3.1 apps (even we don't really support running them). If we have an end-to-end test in SDK for this, then I think it's OK to remove it here, but I think it would be good to have a test somewhere. |
|
Sorry, I should have mentioned in the description - SDK does have tests for this: While the one in this repo does use the live HostModel, it also relies on trying to approximate what the SDK does. I don't think the bundler itself is that risky in terms of churn such that it affects 3.1 behaviour, so I'd rather just rely on the SDK tests. |
These were building a self-contained app targeting netcoreapp3.0/3.1 and then running the single-file bundler on everything in the self-contained publish output directory. With 3.1 having been out of support for nearly a year, I don't think they add much value. We have other tests that target the extraction behaviour via bundler options.