When 'txc env solution import' is pointed at a Build SDK project directory, it runs dotnet build and relogs every output line as [INFO], so packager errors like 'Error: RootComponent validation failed.' are invisible (see TALXIS/tools-devkit-build#47 for the build-side fix).
After the build it picks the newest *.zip from bin/{config}/net462. Two problems: if the current build didn't produce a zip, a stale zip from a previous build gets imported silently. And the net462 path is hardcoded, current TALXIS.DevKit.Build.Sdk outputs to bin/{config}/net472, so the zip isn't found at all.
Fix: classify build output severity when relogging, fail the import when the packager reports errors, only accept a zip written by the current build, and search bin/{config} recursively instead of hardcoding the TFM.
When 'txc env solution import' is pointed at a Build SDK project directory, it runs dotnet build and relogs every output line as [INFO], so packager errors like 'Error: RootComponent validation failed.' are invisible (see TALXIS/tools-devkit-build#47 for the build-side fix).
After the build it picks the newest *.zip from bin/{config}/net462. Two problems: if the current build didn't produce a zip, a stale zip from a previous build gets imported silently. And the net462 path is hardcoded, current TALXIS.DevKit.Build.Sdk outputs to bin/{config}/net472, so the zip isn't found at all.
Fix: classify build output severity when relogging, fail the import when the packager reports errors, only accept a zip written by the current build, and search bin/{config} recursively instead of hardcoding the TFM.