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.

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

Pre-built Intel.Realsense.dll has no version number #2097

Closed
jb455 opened this issue Jul 19, 2018 · 3 comments
Closed

Pre-built Intel.Realsense.dll has no version number #2097

jb455 opened this issue Jul 19, 2018 · 3 comments
Assignees

Comments

@jb455
Copy link
Contributor

jb455 commented Jul 19, 2018

Hi,

I noticed that in at least the last two releases (2.14.0 and 2.13.0.18) available at https://github.com/IntelRealSense/librealsense/releases/, the pre-built Intel.Realsense.dll binaries copied to program files in x86 and x64 are version 0.0.0.0.
In the past (2.10.0), the version number of the file was 1.0.0.0, so now when our installer installs the new version of our software which includes the 2.13 binaries over an old version of our software, it doesn't overwrite the wrapper dll because it thinks a newer version is already there. This leads to the native and wrapper binaries being out of sync.
I know I can pull and build my own copy of the wrapper (after giving it a version number) and include that in our installer, but I think the pre-built binaries should have updated version numbers for people who don't want to build their own.

Thanks!

Edit: in case anyone else runs into this problem before it is officially fixed, you can follow instructions here: https://stackoverflow.com/questions/284258/how-do-i-set-the-version-information-for-an-existing-exe-dll to edit the version number of the dll without having to build it yourself.

@dorodnic
Copy link
Contributor

Hi @jb455
Thanks for pointing that out. I suspect it is related to recent transition to CMake for the .NET wrapper. We will look into it.

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
hi @jb455,

this should be fixed by PR:2267.

@dorodnic
Copy link
Contributor

dorodnic commented Sep 6, 2018

capture
I think we should be good now. Please update here or open a new issue (emails from closed issues sometimes get lost in the pile) if you still see something related.

@dorodnic dorodnic closed this as completed Sep 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants