Ambigious reference for ExtensionAttribute when using Iron Python in Asp.Net

The bug only seems to have been closed because of the DLLs attached to the report, so I think the answer is “no, there isn’t a better way”.

I asked on the bug why it’s closed if the issue still exists, though.