SharpSnmpPro.Mib Release Notes¶
By Lex Li
This page documents major releases of SharpSnmpPro.Mib.
In this article:
Releases¶
2.0.0¶
This is a major release with new platform support. Major changes:
Bug fixes
New Features
- .NET Standard 2.0 support is added .
- RFC 2578 descriptor prefix is supported .
- RFC 2578 restriction on imported items is applied .
- RFC 1155 support is improved .
- Moved a few classes to new namespaces .
- Added overloading methods to ObjectRegistryBase support OID input .
Note
This release depends on #SNMP Library 10.0.2 and above.
1.2.0¶
This is a bug fix release with some new APIs. Major changes:
Bug fixes
- zeroDotZero DisplayEntity.GetObjectIdentifier is fixed .
- jmgt DisplayEntity.GetObjectIdentifier is fixed .
- Table index verification is improved to avoid false alarms .
- Special SMIv1 -> SMIv2 converted TRAP items are properly handled .
- OID resolution is revised to work better with multiple references to the same tree node .
New features
- A new Index type is added and implied flag is supported .
- A new Augments type is added.
- New types such as ContraintedType are added to provide initial constraint related support.
Tutorials on the new features will be added to related sections.
Note
This release depends on #SNMP Library 9.0.5 and above.
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.0.0¶
Initial release.
Product Lifecycle¶
The lifecycle of the releases are listed below,
| Version | Release Date | End-of-life Date |
|---|---|---|
| 2.0.0 | Dec 31, 2017 | N/A |
| 1.2.0 | Jan 16, 2017 | Mar 31, 2018 |
| 1.1.3 | Oct 1, 2016 | Apr 16, 2017 |
| 1.1.2 | Sep 15, 2016 | Oct 1, 2017 |
| 1.1.1 | Jul 14, 2016 | Sep 15, 2017 |
| 1.1.0 | Feb 22, 2015 | Jul 14, 2017 |
| 1.0.0 | Feb 3, 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 contacing technical support team.