Thanks Patrick - it all works now as expected - it seems it was a combination of VS glitch/needing-deep-reset-of-environment and me not realising that I should look for the runtimes folder in Release.

Thank you

Thanks Patrick, it's .NET Framework (net481) so I guess I need to copy native DLLs from the Nuget store. Note that native dlls do not get included during build process into eg bin\Release folder which is unusual. So if I copy native DLLs manually, where should they go then? In the root folder of exe...

I am in the process of upgrading Phidget Nuget from 2024-09-11 to 2025-03-24 using latest VS 2022 (17.13.15). If I use Nuget 2024-09-11 I get the usual 'dll' folder and subfolders in e.g. bin\Debug. However, if I use 2025-03-24, 2025-01, 2024-12 release (possibly any releases in between 2024-09 and ...

Thank you

Would it be possible to set FileVersion and ProductVersion on phidget22.dll files? The dlls don't have this set, I wonder if this could cause issues, e.g. how would Windows know if an existing phidget22.dll in a setup folder needs an update by a newer version or not? I am trying to troubleshoot a po...

I notice with STC1005 and the latest firmware that if I connect via c# to the stepper but do not set TargetPosition immediately (or before its set) reading the TargetPosition will raise a "PhidgetException 0x33 (Unknown or Invalid Value) The value is unknown." I would expect that the drive...

Would it be possible to have full mechanical drawings and a STEP file for the ENC4127_0? The drawings provided do not provide information for various mounting holes used to attach the encoder casing to the motor (x/y position, distance, diameter). I have attached a file that shows some of the missin...

Thanks, I wonder if there is more to it. If you right click on phidgets22.net.dll it will show in details Product version 1.0 but the assembly version will be correct. I think what comes out as product version is AssemblyFileVersion or something on those lines (why Microsoft makes things so complica...

Hi The short version: Phidget22.Net.dll needs to have unique (incremental) product version numbers for automated installers to work properly. Currently I believe the product version is always set to 1.0 which causes installers to break when trying to upgrade Phidget22.Net.dll library. tl;dr I had a ...

Did you get to the bottom of this? I also package Phidget22.dlls manually and always have problems if there is Phidgets Control Panel installed or when upgrading my own software so your last post on potential dependency on Phidgets CP is interesting. It feels as if Phidget APIs have preference to li...