Original report by me.
Some assembly dependencies list some parameters as "*". ManifestEnum treats these as values and adds a duplicate assembly identity with * for that parameter.
It is unclear at the moment how this should be solved. We may not guess how to replace "*" from the dependency alone.
Moreover, ideally we should just keep the ambiguity in the dependency. What if the assembly depends on version "*", and some time later we add another version of the component? But it is not clear how to implement this in the current scheme of the database.
Original report by me.
Some assembly dependencies list some parameters as "*". ManifestEnum treats these as values and adds a duplicate assembly identity with * for that parameter.
It is unclear at the moment how this should be solved. We may not guess how to replace "*" from the dependency alone.
Moreover, ideally we should just keep the ambiguity in the dependency. What if the assembly depends on version "*", and some time later we add another version of the component? But it is not clear how to implement this in the current scheme of the database.