VB -> C#: Conversion duration different between using code converter extension and command line

[Greyfriars]

VB.Net input code

NA

Erroneous output

NA

Expected output

NA

Details

I've install code converter extension and command line to my system.
Also installed VS2022.
Code converter extension version : 9.0.4.0
Code converter CodeConv (command line) version : 9.0.4.493

Converting the same project (VB to C#, Around 180 files).
The duration of conversion between this two tool is different.

For example:
Code Converter extension complete conversion in 5min.
Code Converter command line complete conversion in 30min.

Is this an known issue?

[GrahamTheCoder]

Hi there. Thanks for letting me know. It isn't something I've ever tested. I would have assumed the command line was quicker. Part or all of the difference will probably be in the set up of an msbuildworkspace and a visualstudioworkspace. There may be differences in various pooled resource setups too. It'd be interesting to analyse the difference and see if there is an improvement easily available to the command line (or to both due to the better understanding).
It may be that the msbuildworkspace may contain an interprocess boundary in many calls, which would be insurmountable.

[Greyfriars]

Thanks for the reply. I see that the code i'm trying to convert have more than 100k of lines in a single class and file (~8MB)
I'm using the codeconv -t cs -f -b commandline.

I search one of your comment you mentioned you have tested with a source code with 250k lines.
May i know how long it took for your test?
Thank you.

[GrahamTheCoder]

I'm afraid I can't really remember. I would estimate less than an hour. Though the time of very dependent on size of individual files and certain constructs within them that are intensive to convert