CodeConverter icon indicating copy to clipboard operation
CodeConverter copied to clipboard

Large number of problems trying to convert large VB project in large solution to c#

Open ibelchamber opened this issue 7 months ago • 7 comments

We have a solution with 33 projects, It is currently in UWP + Xaml Islands, as this seems to be not the way forwards now I would like to try to migrate to WinUi3 which does not support VB, so my first step is to convert vb to c#.

First attempt on the first VB project looked quite good, only about 33 errors. Most of these were things going wrong converting subs / functions that had Optional byref parameters. I removed byref in the original VB (was not needed) then A load more came up. Fixed those and retried, then I was up to 364 errors, mostly it seems:

enums have been converted to ints colours are not correctly converted: CS1503 Argument 2: cannot convert from 'Windows.UI.Color' to 'Global.Windows.UI.Color?' there are probably 20 different error types.

It would take days to try to sort this out, but my concern would be that after that, the number of problems will just increase again.

What is the best approach to try to progress this? Would anyone be interested in taking a copy of our solution and investigating the faults? It does seem to be exposing a vast number of issues that maybe obstruct smaller conversions but maybe not as badly,

Thanks.

ibelchamber avatar Nov 22 '23 14:11 ibelchamber