[Closed] passing multiple arguments to dotNet fns without breaking mxs syntax

I have a function in a dotNetClass which converts tif to png.
It takes two fiel path strings as arguments.

in C# it’s called like this:

	myClass.tif2png(infile, outfile)

but in maxscript the syntax it won’t evaluate

myClass =dotNetClass "myClass"
myClass.tif2png(infile, outfile)
-- Syntax error: at ,, expected <factor>
--  In line: myClass.tif2png(infiule, o

elsewhere I’ve been able to do this with one parameter, why does it break with two?