Target older .NET framework by default about packetnet HOT 8 CLOSED

@raspi It looks like 4.5.2 is still supported but 4.5.1 is end-of-life, https://blogs.msdn.microsoft.com/dotnet/2015/12/09/support-ending-for-the-net-framework-4-4-5-and-4-5-1/

what about moving to 4.5.2 instead?

from packetnet.

R2 is supported until 2023 - https://support.microsoft.com/en-us/lifecycle/search?alpha=Windows%20Server%202012%20R2%20Standard . Older NuGet version was using .NET fw 3.5 and sharppcap used that also. For the best backwards compatibility as old as possible .NET fw target should be used. Another way could be to release multiple targets like SQLite does as an example.

from packetnet.

@raspi I think we are talking about two different things. Yes, Windows Server 2012 R2 is supported until 2023, but only .net 4.5.2 is currently supported, not 4.5.1. See https://support.microsoft.com/en-us/lifecycle/search?alpha=Microsoft%20.NET%20Framework%204.5.1

from packetnet.

Yes the .NET fw 4.5.1 might be deprecated (for only ~7 months now) but it doesn't mean that people are running newer version if they're using R2 for example. A lot of people are running .NET fw which was shipped with the OS ie. 4.5.1 in R2 and 8.1.

My use case is OSS LLDP agent which adds LLDP support for older Windows versions so that network and sysadmins jobs are made easier who are still running older OSes in their environments. Their company came up with the policies to not upgrade anything until the OS long term support ends.

from packetnet.

@raspi ahh ok. If it's forwards compatible then I have no problem rebuilding for 4.5.1. Let me check that doing so will work ok here under mono and I can push out a new set of versions sometime in the near future.

from packetnet.

@raspi I've updated the .net target version to 4.5.1. Would you mind testing out the 'net_4_5_1' branch or would it make sense for me to send you .nupack files? I'd like it to be tested prior to bumping versions and releasing new packages etc.

from packetnet.

I was able to compile both packetnet and sharppcap in VS 2017 CE. There were no build or runtime errors with net_4_5_1 branch and my program.

from packetnet.

@raspi published new nuget versions of sharppcap and packetdotnet that target 4.5.1

from packetnet.