Code: Select all
public UserModule()
{
// Do not delete - a parameterless constructor is required!
}
So, is there another reason Ranorex requires an explicit default constructor?
Code: Select all
public UserModule()
{
// Do not delete - a parameterless constructor is required!
}
No, Ranorex just needs a parameterless constructor to create the module at runtime. So the code for the parameterless constructor is there in case you define a second constructor with parameters. You can safely delete the parameterless constructor if you make sure, you don't create a constructor with parameters.dankod wrote:So, is there another reason Ranorex requires an explicit default constructor?