Migrated VB Apps: Binding DataTable Columns still does not work

Feedback Apps
, , , ,
3

And this is something related and therefore posting it in this thread. I have confirmed this
by making deliberate changes to the process arguments.

Just as I migrated the App, I also migrated its related Automation project to Windows.

After the migration, this is what I noticed in the Main.xaml.json file:

Any argument added or renamed in the migrated solution does not have a Widget type:

The image shows a JSON configuration file with key-value pairs defining attributes for three different outputs, each highlighted with a yellow cross mark next to the "Widget" attribute set to null. (Captioned by AI)
The image shows a JSON configuration file with key-value pairs defining attributes for three different outputs, each highlighted with a yellow cross mark next to the "Widget" attribute set to null. (Captioned by AI)850×1665 46.7 KB

And anything that was left untouched after the migration has a valid Widget type:

This image shows a JSON snippet defining arguments with properties such as "Name," "DisplayName," "Widget," "IsRequired," and others, where green checkmarks indicate the "Widget" values set as "Number" or "TextComposer." (Captioned by AI)
This image shows a JSON snippet defining arguments with properties such as "Name," "DisplayName," "Widget," "IsRequired," and others, where green checkmarks indicate the "Widget" values set as "Number" or "TextComposer." (Captioned by AI)862×1570 56.9 KB

I’m hoping this is not going to be a problem with project migrations?

Thanks