Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
wrong ProductVersion using AssemblyInformationalVersion, AssemblyFileVersion and AssemblyVersion attributes
See original GitHub issueProductVersion number should be set using the following fallback sequence (as msdn doc and c# compiler behaviour):
- AssemblyInformationalVersionAttribute
- AssemblyFileVersionAttribute
- AssemblyVersionAttribute
repro:
-
create both a f# Library and c# ClassLibrary
-
set version attributes in both c# and f#
[<assembly: AssemblyVersion("1.2.0.0")>] [<assembly: AssemblyFileVersion("1.3.0.0")>] -
build and check version
expected 1.3.0.0, actual 1.2.0.0
this issue was reported by @haf in fsharp/fsharp#289. I fixed only the warning message with Microsoft/visualfsharp#298
This bug report got lost in the migration openrepo -> codeplex -> github.
Issue Analytics
- State:
- Created 8 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Why AssemblyFileVersion automatically changes Product ...
I assumed as I changed AssemblyVersion, the installer automatically detects the latest DLL and replace at the time of upgrade. But, upgrade ...
Read more >Use AssemblyVersion and AssemblyFileVersion attributes
AssemblyInfo.cs provides two attributes to set two different types of versions. This tip shows how to use those two attributes. Microsoft .
Read more >Assembly Information – Version Related Attributes
It talks about the three different assembly version attributes in detail, demonstrates each with example code and output, and suggests some ...
Read more >What is the difference between Version, AssemblyVersion ...
Version is equivalent to the old [AssemblyInformationalVersion] attribute and can technically be anything (i.e Hamburger ), but you generally ...
Read more >Minor Upgrade does not update file if ProductVersion of the ...
In a regular file location, AssemblyFileVersion should be the correct item - whatever changes the version that shows up in Explorer properties.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Why on earth would F# want to replicate the C# behavior so exactly as to replicate the unnecessary and confusing warning (which can’t be disabled: https://github.com/Microsoft/visualfsharp/issues/3139 )?
https://github.com/Microsoft/visualfsharp/pull/618/files#diff-c1c59f2c3f2ed83115462d37e87f6635R60 is wrong I think; having a version like
1.2.3-betais what the informational version is for, no?