Hello XJ,
Sorry for the delayed response, but we've been working on your issue in the past week or so. We've identified the reason why your assembly has unresolved components. Here is a likely scenario:
- Open an assembly
- Assume the network is bad, due to which there was a problem downloading one of the referenced files
- The assembly opens with a warning about an unresolved component
- Ignore the warning, edit the assembly and save
- Close and reopen
The assembly will now open in an unresolved state even if the network connectivity is good.
Unfortunately, saving the assembly in an unresolved state will permanently leave that assembly in an unresolved state. We're debating whether to disable save on such assemblies, or simply warn the user about it, but still allow him to save it. Let us know your thoughts.
At this point, unfortunately, your bad assembly cannot be repaired. Our apologies for the inconvenience. I hope you'll be able to continue by promoting a previous version.
Thx
Ahsan
Ahsan Ali
Fusion Senior Software Architect