using deprecated IControl methods with upgraded server (11)

Hi Adrian,

 

 

Most of the time when they deprecate the methods and only keep them around for backward compatibility for the iControl Assembly and they will not work in higher versions because they've changed the access methods.

 

 

Example:

 

In v10.x.x you would access a Pool Member with the CommonIPPortDefinition, but in v11.x.x you have to access it with CommonAddressPort.

 

 

For anything you have that uses methods that deprecated I would suggest making getting ready to update them, or make your application v10/v11 aware and select which method to use based on the version of BIG-IP that you are connecting to.

Michael is right on. We mark methods as deprecated when we need to make an underlying change to the configuration objects that make the method parameter not make sense anymore. A good example is when we moved from IP addresses to user friendly names for some of our objects. We do our best to "make" the deprecated methods work but we do reserve the right to remove them a year after we mark them deprecate. The main reason for that is that in some cases, we cannot make the deprecated methods parameters work due to various factors. In most cases, they are left in the APIs, but they could go away someday.

 

 

For your case, I'd do what you can to move away from them if you can. Also, make sure you test anything during your upgrade process.

 

 

-Joe