I'm not sure how the tests wouldn't have caught this bug.
I have a.net class that has the functionAddQuery with the following method signatures.

AddQuery    Void AddQuery(api.QueryType)...    Void AddQuery(System.Object)...

whereQueryType is another custom object type.

On2.0 and2.1dev1 the function works as expected.

• I can pass aQueryType object toAddQuery and it would call the first method.
• CallingAddQuery with astring orint would use the second method and process them.

On2.1.0 and the earliest archived copy inappveyor this behavior changed.

• PassingQueryType object toAddQuery still works.
• Passingstring type toAddQueryerrors withNo method matches given arguments

I've tested onPython 2.7,Python 3.5 both x64.
Looks like Pythonnet is no longer identifyingstringint and other types to be of typeSystem.Object as well.