Skip to content

Bug: Obsfucated assemblies does not provide a valid AssemblyInformationalVersionAttribute #245

@peters

Description

@peters

I forgot to report this, but all our programs are obsfucated. Therefore when we call update manager, there is always new releases to apply because assembly version to shimmer is reported as 0.0.0 when it's actually, i.e 1.2.3102.

The problem can easily be solved by adding a parameter overload accepting a "here is my real assembly version" version :)

Today we solve it by manually resolving the update graph ourselfs by excluding any prior versions to currentVersion

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions