Reply to thread

Message

<blockquote data-quote="henso" data-source="post: 914162" data-attributes="member: 119106">I don't think that would be practical. Some of the physical devices are able to see all the published devices and there could be many if there is one per manufacturer.I propose a solution as follows (in DvDevice.cs):[CODE]public delegate void GetDeviceInfoForEndpointDlgt(EndpointConfiguration config, ref ILocalizedDeviceInformation deviceInfo);public class DvDevice : IDisposable{&nbsp; public GetDeviceInfoForEndpointDlgt DeviceInfoHook = null;&nbsp; ...&nbsp; internal void AddDeviceDescriptionsRecursive(XmlWriter writer, EndpointConfiguration config, CultureInfo culture)&nbsp; {&nbsp; &nbsp; &nbsp; ...&nbsp; &nbsp; &nbsp; GetDeviceInfoForEndpointDlgt dih = DeviceInfoHook;&nbsp; &nbsp; &nbsp; ILocalizedDeviceInformation deviceInformation = null;&nbsp; &nbsp; &nbsp; if (dih != null)&nbsp; &nbsp; &nbsp; &nbsp; dih(config, ref deviceInformation);&nbsp; &nbsp; &nbsp; if (deviceInformation == null)&nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; deviceInformation = _deviceInformation;&nbsp; &nbsp; &nbsp; }&nbsp; &nbsp; &nbsp; ...&nbsp; }&nbsp; ...}[/CODE]&nbsp;I can then link device information to endpoint configuration and saved it a file. Next time the device is published this information is already loaded and then I can override the device information sent depending on endpoint configuration. Would this be possible? <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite26" alt=":unsure:" title="Unsure&nbsp; &nbsp; :unsure:" loading="lazy" data-shortname=":unsure:" />&nbsp;&nbsp;The device information needed will of course be defined in a config file, so no recompiles should be needed. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" /></blockquote>

[QUOTE="henso, post: 914162, member: 119106"] I don't think that would be practical. Some of the physical devices are able to see all the published devices and there could be many if there is one per manufacturer. I propose a solution as follows (in DvDevice.cs): [CODE] public delegate void GetDeviceInfoForEndpointDlgt(EndpointConfiguration config, ref ILocalizedDeviceInformation deviceInfo); public class DvDevice : IDisposable { public GetDeviceInfoForEndpointDlgt DeviceInfoHook = null; ... internal void AddDeviceDescriptionsRecursive(XmlWriter writer, EndpointConfiguration config, CultureInfo culture) { ... GetDeviceInfoForEndpointDlgt dih = DeviceInfoHook; ILocalizedDeviceInformation deviceInformation = null; if (dih != null) dih(config, ref deviceInformation); if (deviceInformation == null) { deviceInformation = _deviceInformation; } ... } ... } [/CODE] I can then link device information to endpoint configuration and saved it a file. Next time the device is published this information is already loaded and then I can override the device information sent depending on endpoint configuration. Would this be possible? :unsure: The device information needed will of course be defined in a config file, so no recompiles should be needed. ;) [/QUOTE]

Verification