search

dotpcap / sharppcap

Official repository - Fully managed, cross platform (Windows, Mac, Linux) .NET library for capturing packets
1.33k stars 268 forks source link

It's not compatible? #44

Closed RobbieW69 closed 5 years ago

RobbieW69 commented 6 years ago

Severity Code Description Project File Line Suppression State Error Could not install package 'SharpPcap 4.5.0'. You are trying to install this package into a project that targets '.NETFramework,Version=v3.5', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author. 0

RobbieW69 commented 6 years ago

What version of the .net framework do I need?

chmorgan commented 6 years ago

You’ll want to use either .net framework 4.6.1 or later, or .net standard, I think 2.0.

Keep in mind that mono is still required for cross platform support on Mac and Linux. I’m working on fixes for dotnet support on these platforms but not sure when I’ll get to it.

On Thu, Apr 19, 2018 at 3:39 PM Robbie W. notifications@github.com wrote:

What version of the .net framework do I need?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/chmorgan/sharppcap/issues/44#issuecomment-382856595, or mute the thread https://github.com/notifications/unsubscribe-auth/ABJ-AFnn4pyZcIqEau6hSwFsUIxQQsJiks5tqOftgaJpZM4TcYAe .

lextm commented 5 years ago

Though most people should have already upgraded to .NET Framework 4.6.1 and above (so .NET Standard 2.0 is not a problem), Microsoft stills supports .NET Framework 4.5.2 and above. It is still ideal to ship a .NET Framework 4.5 compatible assembly.

chmorgan commented 5 years ago

@lextm any idea how much work it would be to reenable building for 4.5? I think I upgraded because the Mac visual studio was having issues with the older build target.

lextm commented 5 years ago

@chmorgan actually it is quite simple,

No other changes are needed.

chmorgan commented 5 years ago

@lextm I merged that net45 target change. Appveyor should auto-build and deploy to nuget but I'm not sure exactly how that might work on the package or deployment side.

lextm commented 5 years ago

@chmorgan I am not familiar with AppVeyor deployment. But based on the log https://ci.appveyor.com/project/chmorgan/packetnet/builds/22588493 the generated package is still of version 0.20.0. You might need to bump the version to 0.21.0 to trigger another deployment.

chmorgan commented 5 years ago

Ahh right. I’ve been occupied with other tasks. If someone wants to submit a pr to update the version that would speed things up. Not sure when I’ll be able to get back to it otherwise.

Chris

On Sun, Feb 24, 2019 at 11:41 AM Lex Li notifications@github.com wrote:

@chmorgan https://github.com/chmorgan I am not familiar with AppVeyor deployment. But based on the log https://ci.appveyor.com/project/chmorgan/packetnet/builds/22588493 the generated package is still of version 0.20.0. You might need to bump the version to 0.21.0 to trigger another deployment.

— You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub https://github.com/chmorgan/sharppcap/issues/44#issuecomment-466792790, or mute the thread https://github.com/notifications/unsubscribe-auth/ABJ-ALdpm_zkvd35yAI4y_2Q0yfVq6LUks5vQsCxgaJpZM4TcYAe .

chmorgan commented 5 years ago

Closing as sharppcap 4.6.0 and new packetdotnet have been released.