I downloaded the most recent version of the demo driver, compiled it, and put it in the right folder. When i log at the driverscan log of the recording server it checks the folder and nothing gets loaded. The weird part is, i have a older compiled version of the demodriver that gets loaded fine when i put it in the folder (and remove the other one)
I removed the cache file and contents of the “offline” folder. Rebooted the system and pretty much tried everything. Even changed all the GUIDs just to be sure. The freshly build version never shows up, the old one works fine ( what i never saved the source for, so that one is one me )
Edit : 2022 R3 is used.
I would like to try to reproduce this in the Milestone Test lab. I would like to be sure I understand what versions. The XProtect VMS and the Recording server is 2022R3, and the newest version of the Demo Driver sample gets build using the newest version of the MilestoneSystems.VideoOS.Platform.DriverFramework NuGet which is 23.2.1?
Please confirm the versions or correct me..
Hello, i am facing the same issue so far. I do confirm that i have the versions that you have mentioned but the demodriver does not appear. Note: other custom drivers work well. Thank u
I wish I had been thinking the right thoughts.. I do not need to test. New functionality was introduced.
MIP SDK 2023 R1 release note mentions..
Driver framework
- Third-party device drivers are now supported in the Express mode add-hardware wizard in the Management Client and Configuration API. Supported discovery schemes are UPnP, Ping/ARP, mDNS and ONVIF. The SupportedSchemes property on DriverInfo specifies which scheme(s) to use.
https://doc.developer.milestonesys.com/html/index.html?base=gettingstarted/mip2023r1_intro.html&tree=tree_home.html
This means that a Driver Framework driver built with 2023 R1 or R2 will not work on a 2022 R3 recording server.
To support 2022 R3 please use sample and NuGet for 2022 R3.