Legacy-Obsolescence
- HostAccess®
- Hydra
- LEIF/HydraExpress
- NobleNet RPC
- Nouveau
- RW Metro
- SourcePro® C++
- Stingray®
- XML Corba Link
- XML DB Link
- XML Object Link
|
HostAccess 7.40e |
With the release of HostAccess 7.40g on September 28th, 2009 HostAccess 7.40e has been placed into obsolescence. During this time, licenses can be purchased only for added developers working on existing projects, and technical support assistance remains available under existing support contracts. In addition all previous versions are officially retired. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.40d |
With the release of HostAccess 7.40f on April 30th, 2009 HostAccess 7.40d has been placed into obsolescence. During this time, licenses can be purchased only for added developers working on existing projects, and technical support assistance remains available under existing support contracts. In addition all previous versions are officially retired. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.40c |
With the release of HostAccess 7.40e on March 11th, 2009 HostAccess 7.40c has been placed into obsolescence. During this time, licenses can be purchased only for added developers working on existing projects, and technical support assistance remains available under existing support contracts. In addition all previous versions are officially retired. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.40b |
With the release of HostAccess 7.40d on August 26th, 2008 HostAccess 7.40b has been placed into obsolescence. During this time, licenses can be purchased only for added developers working on existing projects, and technical support assistance remains available under existing support contracts. In addition all previous versions are officially retired. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.40a |
With the release of HostAccess 7.40c on April 16th, 2008 HostAccess 7.40a has been placed into obsolescence. During this time, licenses can be purchased only for added developers working on existing projects, and technical support assistance remains available under existing support contracts. In addition all previous versions are officially retired. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.30f |
With the release of HostAccess 7.40b on November 9th, 2007, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on November 9, 2008. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.30e |
With the release of HostAccess 7.40a on July 18, 2007 these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on July 18, 2008. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.30d |
With the release of HostAccess 7.30f on May 25, 2007 these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on May 25, 2008. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.30c |
With the release of HostAccess 7.30e on March 5, 2007, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on March 5, 2008. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.30b |
With the release of HostAccess 7.30d on December 20, 2006, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on December 20, 2007. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.30 |
With the release of HostAccess 7.30c on September 7, 2006, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on September 7, 2007. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
HostAccess 7.2 |
With the release of HostAccess 7.3 on September 2, 2005, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on September 2, 2006. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
Hydra 4.3 |
With the release of Hydra 4.5 on August 3, 2009, HydraEnterprise 4.3 has been placed into obsolescence. During this time, licenses can be purchased only for added developers working on existing projects, and technical support assistance remains available under existing support contracts. For more information, please read our Obsolescence Policy |
|
Hydra 4.0 |
With the release of Hydra 4.3 on February 19, 2009, HydraEnterprise 4.0 has been placed into obsolescence. During this time, licenses can be purchased only for added developers working on existing projects, and technical support assistance remains available under existing support contracts. For more information, please read our Obsolescence Policy |
|
HydraSCA 3.5 |
With the release of Hydra 4.0 on October 28, 2008, HydraEnterprise 3.5 has been placed into obsolescence. During this time, licenses can be purchased only for added developers working on existing projects, and technical support assistance remains available under existing support contracts. In addition all previous versions are officially retired. For more information, please read our Obsolescence Policy |
|
LEIF 3.5 |
With the release of HydraExpress 4.0 on October 28, 2008, LEIF 3.5 has been placed into obsolescence. During this time, licenses can be purchased only for added developers working on existing projects, and technical support assistance remains available under existing support contracts. In addition all previous versions are officially retired. For more information, please read our Obsolescence Policy |
|
LEIF 2.5.1 |
With the release of LEIF 3.5 on May 25, 2007, LEIF 2.5.1 was placed into obsolescence and, after a one year period, was retired on May 25, 2008. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy |
|
LEIF 2.5 |
With the release of LEIF 2.5.1 on January 10, 2006, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on January 10, 2007. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy |
|
LEIF 2.2 |
With the release of LEIF 2.5 on July 12, 2005, LEIF 2.2 has been placed into obsolescence. During this time, licenses can be purchased only for added developers working on existing projects, and technical support assistance remains available under existing support contracts. For more information, please read our Obsolescence Policy |
|
LEIF 2.1 |
With the release of LEIF 2.2 on November 15, 2004, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on November 15, 2005. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
LEIF 2.0 |
With the release of LEIF 2.1.0 on June 17, 2004, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on June 17, 2005. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
LEIF 1.2 |
With the release of LEIF 2.0 on March 10, 2004, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on March 10, 2005. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
LEIF 1.0 |
With the release of LEIF 1.2 on August 13, 2003, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on August 13, 2004. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
NobleNet RPC |
As of November 26, 2001, Rogue Wave has retired NobleNet RPC and NobleNet RPCGen. Support contracts will be honored until they expire, but will not be renewed. New or additional development or deployment licenses will not be sold. For more information, please read our Obsolescence Policy. |
|
Nouveau |
As of October 16, 2001, Rogue Wave has retired Nouveau. Support contracts will be honored until they expire, but will not be renewed. New or additional development or deployment licenses will not be sold. For more information, please read our Obsolescence Policy. |
|
RW Metro |
RW-Metro entered into Obsolescence on November 30, 2000 and was retired on November 30, 2001. For more information on support for these products, please contact Technical Support. For more information, please read our Obsolescence Policy. |
|
SourcePro® C++ Edition 10 update 1 |
With the release of SourcePro C++ Edition 11 on September 21, 2009 these versions of the SourcePro(r) C++ products were placed into obsolescence and, after a one year period of obsolescence, will be retired on September 21, 2010. For more information, please read our Obsolescence Policy. |
|
SourcePro® C++ Edition 10 |
With the release of SourcePro C++ Edition 10 update 1 on July 25, 2008 these versions of the SourcePro(r) C++ products were placed into obsolescence and, after a one year period of obsolescence, were retired on July 25, 2009. For more information, please read our Obsolescence Policy. |
|
SourcePro® C++ Edition 9u1 |
With the release of SourcePro C++ Edition 10 on December 18, 2007 these versions of the SourcePro(r) C++ products were placed into obsolescence and, after a one year period of obsolescence, will be retired on December 18, 2008. For more information, please read our Obsolescence Policy. |
|
SourcePro® C++ Edition 9 |
With the release of SourcePro C++ Edition 9u1 on July 10, 2006 these versions of the SourcePro(r) C++ products were placed into obsolescence and, after a one year period of obsolescence, were retired on July 10, 2007. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
SourcePro® C++ Edition 8 |
With the release of SourcePro C++ Edition 9 on January 24, 2006 these versions of the SourcePro® C++ products were placed into obsolescence and, after a one year period of obsolescence, were retired on January 24, 2007. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
SourcePro® C++ Edition 7 |
With the release of SourcePro C++ Edition 8 on July 28, 2005 these versions of the SourcePro® C++ products were placed into obsolescence and, after a one year period of obsolescence, were retired on July 28, 2006. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
SourcePro C++ Edition 6 |
With the release of SourcePro C++ Edition 7 on August 4, 2004, these versions of the SourcePro C++ products were placed into obsolescence and, after a one year period of obsolescence, were retired on August 4, 2005. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
SourcePro C++ Edition 5 |
With the release of SourcePro C++ Edition 6 on August 15, 2003, these versions of the SourcePro C++ products were placed into obsolescence and, after a one year period of obsolescence, were retired on August 15, 2004. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
SourcePro C++ Edition 4 |
With the release of SourcePro C++ Edition 5 on May 19, 2003, these versions of the SourcePro C++ products were placed into obsolescence and, after a one year period of obsolescence, were retired on May 19, 2004. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
SourcePro C++ Edition 3 |
With the release of SourcePro C++ Edition 4 in the Fall of 2002, these versions of the SourcePro C++ products were placed into obsolescence and, after a one year period of obsolescence, were retired in the Fall of 2003. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
SourcePro C++ Edition 2 |
With the release of SourcePro C++ Edition 3 in the Winter of 2002, these versions of the SourcePro C++ products were placed into obsolescence and, after a one year period of obsolescence, were retired in the Winter of 2003. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
SourcePro C++ Edition 1 |
With the release of SourcePro C++ Edition 2 in the Fall of 2001, these versions of the SourcePro C++ products were placed into obsolescence and, after a one year period of obsolescence, were retired in the Fall of 2002. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
Analytics.h++ |
Our .h++ product line entered into obsolescence effective May 1, 2001, coinciding with the launch of Rogue Wave SourcePro C++. SourcePro C++ integrates existing functionality with an array of new and refined features and is designed to facilitate an easy transition for applications built with .h++ products. After a one year period of obsolescence, the .h++ products were retired on May 1, 2002. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
Stingray Studio 10.1: |
As of September 21, 2009, Stingray Studio 10.1 will enter the 1 year obsolescence period. We will honor current support contracts until they expire. For more information, please read our Obsolescence Policy. With the release of Stingray Studio 10.2 on September 21, 2009, these versions were placed into obsolescence that will result in their retirement on September 21, 2010. |
|
Stingray Studio 10: |
As of January 20 2009, Stingray Studio 10 will enter the 1 year obsolescence period. We will honor current support contracts until they expire. For more information, please read our Obsolescence Policy. With the release of Stingray Studio 10.1 on January 20, 2009, these versions were placed into obsolescence that will result in their retirement on January 20, 2010. |
|
Stingray Studio 2006 version 2: |
As of April 16 2008, Stingray Studio 2006 version 2 will enter the 1 year obsolescence period. We will honor current support contracts until they expire. For more information, please read our Obsolescence Policy. With the release of Stingray Studio 10 on April 16, 2008, these versions were placed into obsolescence that will result in their retirement on April 16, 2009. |
|
Stingray Studio 2006: |
With the release of Stingray Studio 2006 version 2 on December 6, 2006, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on December 6, 2007. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
Stingray Studio 2004 version 2: |
With the release of Stingray Studio 2006 on February 23, 2006, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on February 23, 2007. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
Stingray Studio 2004: |
With the release of Stingray Studio 2004 version 2 on April 22, 2005, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on April 22, 2006. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
Stingray Studio 2003: |
With the release of Stingray Studio 2004 on March 24, 2004, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on March 24, 2005. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
Stingray Studio 2002: |
With the release of Stingray Studio 2003 on June 26, 2003, these versions were placed into obsolescence and, after a one year period of obsolescence, were retired on June 26, 2004. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
Objective Grid |
As of August 24, 2001, the functionality found in these Stingray products has been incorporated into the Rogue Wave Stingray Studio. All of these products are no longer available for individual purchase, but are offered as part of one integrated product. |
|
UML Studio |
As of August 24, 2001, these Stingray products have been retired. |
|
XML-DB Link |
As of April 15, 2003, Rogue Wave has retired XML-DB Link and XML-CORBA Link. No new or additional licenses will be sold. Support contracts will not be renewed. For more information, please read our Obsolescence Policy. |
|
XML Object Link 1.2 |
With the release of LEIF 2.0 on March 10, 2004, these versions of XML Object Link were placed into obsolescence and, after a one year period of obsolescence, were retired on March 10, 2005. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
XML Object Link 1.1 |
With the release of XML Object Link 1.2 on August 14, 2003, these versions of XML Object Link were placed into obsolescence and, after a one year period of obsolescence, were retired on August 14, 2004. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |
|
XML Object Link 1.0 |
With the release of XML Object Link 1.0 on January 14, 2003, these versions of XML Object Link were placed into obsolescence and, after a one year period of obsolescence, were retired on January 14, 2004. Accordingly, Rogue Wave no longer provides standard technical support for these versions. Custom support is available on a case by case basis. For more information, please read our Obsolescence Policy. |