SharpSnmpPro.Mib Release Notes

This page documents major releases of SharpSnmpPro.Mib.

Releases

3.0.0 (Private Beta)

This is a major release with new platform support. Major changes:

Bug fixes

  • Fixed a few parsing edge cases.

New Features

  • C# 8.0 support (nullable annotation).

2.1.3

This is a bug fix release. Major changes:

Bug fixes

2.1.2

This is a bug fix release. Major changes:

Bug fixes

2.1.1

This is a bug fix release. Major changes:

Bug fixes

2.1.0

This is a bug fix release. Major changes:

Bug fixes

New Features

Removed Features

  • .NET Core 1.0 and 1.1 support expires.

Note

This release depends on C# SNMP Library 12.1.0 and above.

2.0.0

This is a major release with new platform support. Major changes:

Bug fixes

New Features

Note

This release depends on C# SNMP Library 10.0.2 and above.

1.2.0

This is a bug fix release with some new APIs. Major changes:

Bug fixes

New features

Tutorials on the new features will be added to related sections.

Note

This release depends on C# SNMP Library 9.0.5 and above.

1.1.3

This is a bug fix release. Major changes:

1.1.2

This is a bug fix release. Major changes:

1.1.1

This is a bug fix release. Major changes:

  • .NET Framework 4.0 is no longer supported. .NET 4.5 and above is required.

1.1.0

This is a bug fix release. Major change:

  • More internal types are now exposed as public.

1.0.0

Initial release.

Product Lifecycle

The lifecycle of the releases are listed below,

Version

Release Date

End-of-life Date

2.1.x

Oct 04, 2020

N/A

2.0.0

Dec 31, 2017

Jan 05, 2021

1.2.0

Jan 16, 2017

Mar 31, 2018

1.1.3

Oct 01, 2016

Apr 16, 2017

1.1.2

Sep 15, 2016

Oct 01, 2017

1.1.1

Jul 14, 2016

Sep 15, 2017

1.1.0

Feb 22, 2015

Jul 14, 2017

1.0.0

Feb 03, 2014

Feb 22, 2016

The old rule (1.0.0-1.1.2) is that any release will be actively supported till its next release becomes one year old.

The new rule (1.1.3 and above) is that any release will be actively supported till its next release becomes three months old. This change is to match our more frequent release cycles.

Users of expired releases must upgrade to an active supported release before contacting technical support team.