Hi Paul,

I'll book out some time over the Weekend to update the library,
will ping you once done.

Marcus

Well here is my current environment.

• Visual Studio 2022
• Target Framework: .NET Framework 4.8
• Microsoft .NET SDK 9.0.308 installed

Until now I've never had the need to upgrade past 4.8. The problem is that nothing past 4.8.1 is available in my project build options. I'm looking into the issue but haven't found a clear-cut answer. I'm willing to update in the future, but right now I'd rather not add one more complication to this project. Would it be possible for you to create one more project update at the current level, then drop support in a subsequent release?

-p

The versioning issue might be a moot point since I compile the ZWAVEJS.NET source as a library within my project ...

Hi@pnpebeling,

V4 will be getting 1 last bump to the current schema (working on it right now), then after that, I will be looking to bump to v5 shortly after - where it will drop support fornet48,netstandard2.0 - and target only those above (and will keep in line with modern framework versions thereafter)

It is in use by The HomeSeer project - and they have been warned, and will be keeping a private version of V4, as their product cant go pastNet48 due to their customer base - so they will maintain their own fork past V4.

Moving forward (after the last update)

If you cant move past NET48 - keep a fork of V4, and update it, accordingly, when new versions of the driver / server are released - but it will be your own code base - more then happy to guide you when you need to update functions or other things.

if you want to stay inline with the official project, and use it's code base as is, it will only support NET6+

v5 will lose the internal web socket source - and use the official library it is based of (which does not support <NET6)

tl;dr
The next update I make to V4will contain the latest driver + a few updates - but after that (v5) will drop support for anything below <NET6, so you will see v4 get the latest Driver version.

The reason you will have to maintain your fork of V4 (if cant move pastNET48) - is due to the web socket lib, and the fact the current lib does not support < .NET6

v4 - holds onto source code for the web socket (which at the time of embedding, did support <NET48)
v5 - will switch to the official lib which only supportsNET6+

Hope that makes sense

Thanks. Makes perfect sense.

-p

I will tag you once V4 has been updated - trying to get it done before Monday