cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade Causes API Inconsistencies

Former Member
0 Kudos

I successfully upgraded Web Tools from 625 to 652 (SP1 PL2). The problem is, many of the API calls have had their parameters changed, which are causing build errors. Below are some code examples, the problems defined, and the compiler errors relating to them.


List<NPOrderExpenseDiscount> list = new List<NPOrderExpenseDiscount>();
list.AddRange(discount.Discount.GetCurrentDiscounts(this._order.getNPOrder(), ox));

No overload for method 'GetCurrentDiscounts' takes '2' arguments

This code will compile under 625, but in 652 the GetCurrentDiscounts declaration requires a third bool parameter.


ListPrice(ref price, "@pricelist", parameters2,
  priceList.ListFactor, connectionString, theTrace);

Argument '4': cannot convert from 'decimal' to 'double'

Again, OK in 625, but in 652 the fourth argument, priceList.ListFactor, is no longer of type decimal but of type double.


this._order.BillingAddressID = this.AddAddress.Save();

No overload for method 'Save' takes '0' arguments

In 625, this ran fine, but in 652 the Save function requires at least one parameter.


this.AddAddress.BillingOnly = true;

'netpoint.common.controls.AddressBlock' does not contain a definition for 'BillingOnly'

625 has AddAddress having a property BillingOnly - in 652, the property seems to have mysteriously vanished.

-


As you can see, there are several problems with the API differences that I am trying to reconcile. Is there any sort of documentation where I can see the changes made in the API? The .chm file included with the SDK doesn't seem to have them all.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Micheal

I believe we talked about this in the web tools class last year, but if you're going to be doing customizations based on the web tools API then you would need to implement source control before you start so you can see what has changed.

625 to 652 is a huge change and many many files changed in 10 month period in between these two patches. 625 was not even the production release patch and was used during rampup of which there were 5 more patches after, before SP0 was released in July of 2008.

Former Member
0 Kudos

Yeah, I'm not in charge of these changes, our consultants are, and as far as I know they did not implement such a change list.

So my fears of no API being available are correct then. Seems like something that somebody would have posted to a wiki article...maybe I'll start one...

I wonder though, is there any documentation for versions from after the production release came out - v630, was it? - until the latest version, v652?

Former Member
0 Kudos

The API documentation is updated when it is changed many changes were made in the SP0 version from any version in Ramp Up and the changes during rampup were not documented.

When SP1 came out there were more API changes and the documentation should have been updated and released with the new information in it as well. However, there is no before->after API document. Each patch that is released with the exception of SP1 comes with a list of files that were modified and care is taken to not make drastic changes to the API during a regular(non-service pack) patch release.

Former Member
0 Kudos

Thanks for your help, Bryce. This is very insightful.

Answers (0)