Calling regasm from .NET Framework 4.0 generates an error for a DLL that is on a mapped network share. This occurs during our debug builds on developer machines (we actually call a utility that wraps around regasm to perform COM-based registration).
The error is:
RegAsm : error RA0000 : Could not load file or assembly 'file:///m:\<file being regasmed>' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
I can work around this issue by modifying regasm.exe.config to include the loadFromRemoteSources element. This seems like an annoying change for something that seems like a fairly common task.
Is there some better way to enable this?
View Complete Post