Closed ujhelyiz closed 12 years ago
As I have seen, the issue is caused by the fact that EPackages from the EPackage registry are not contained in a resource.
As for these resources the default serialization might be used, I simply added a check to avoid this issue. @CMark please, review the solution then close the ticket.
Yes, the null check fixes the problem. If no EResource, we can't determine the URI, so we can't replace it. I am closing the issue.
@szabta89 reported this exception trace yesterday in the mailing list, that happens periodically.