Converting project targetting x86 platform changes platform to AnyCPU and creates mismatch with the solution configuration

[momchilstefanov]

I'm not sure if the issue is with try-convert or Visual Studio but in Visual Studio 2019 16.8.3:

1. Create WPF .NET Framework app with the Visual Studio project template.
2. Change solution and project configurations to target x86 platform (they are AnyCPU from the project template)
3. Run command try-convert -p WpfApp.csproj -tfm netcoreapp3.1 --no-backup

As a result the project is shown as having AnyCPU target platform, Visual Studio shows warning that the project and solution have different configurations and when building the solution the project is skipped from building.

Here is the project I've reproduced it with but I would expect that following the steps everyone will have the same result.

The csproj still has his x86 configurations defined but Visual Studio is recognizing it as AnyCPU.

Thanks, Momchil

[cartermp]

Tentatively labeling as a bug. Although we're respecting the configuration during conversion, the fact that the project system isn't picking it up likely implicates try-convert in doing something subtly wrong.