Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
peters opened this issue Mar 28, 2014 · 0 comments
Open

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

peters opened this issue Mar 28, 2014 · 0 comments

Comments

@peters
Copy link
Contributor

peters commented Mar 28, 2014

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@peters