search

libplctag / libplctag.NET

A .NET wrapper for libplctag.
https://libplctag.github.io/
Mozilla Public License 2.0
217 stars 54 forks source link

Net Framework 4.5 #409

Closed t1a2l closed 2 months ago

t1a2l commented 2 months ago

it seems it is required to have 3.1, i have a working project with 4.5 and changing it back down is not an option, any solution, are you going to support 4.5?

timyhac commented 2 months ago

Hi there - I think what you are saying is that you

Changing it down is not an option

.NETCore 3.1 is more recent than .NET Framework 4.5 - both of these have reached End of Life by Microsoft.

There are multiple versions of ".NET" - the two that are usually discussed are

.NET Framework 4.5 has not been supported by Microsoft since 2016, whereas .NETCore 3.1 was only released in December 2019 and reached end of life Dec 2022. .NETCore was rebranded to .NET when moving from 3.1 to 5 - so you will see it as NETCore 3.1, and NET5.0

are you going to support 4.5?

The project has always (up until the recent libplctag-v1.6.0-alpha.0) targeted NETStandard2.0, which is able to be used by certain versions of NETFramework in addition to NETCore and .NET and NETFramework 4.5 is not one of them.

So if my assumption is correct that you have been successfully using libplctag-v1.5.2 for a NETFramework4.5 project - I'm not sure how that has been working.

Having said that, if there is a good reason to add support for NetFramework4.5 then I am open to that but I believe there would be additional testing capabilities which I currently don't have easy access to.

MountainKing91 commented 2 months ago

In hope it helps somehow, all my recent tests and projects with libplctag are developed using .NET Framework 4.8, which is supported by .NET Standard 2.0 as @timyhac's link states and these days it is also already installed on Windows 10 by default - this comes handy.

@t1a2l Is there any chance you can upgrade from 4.5 to 4.8?

timyhac commented 2 months ago

@t1a2l - I trust that this has answered your question, and I agree with @MountainKing91 - upgrading to a supported version of .NET is preferable. If you do have a good reason to add supported for end-of-life versions of .NET please let us know.