download of project wont compile


The link to the download and the project when unzipped, doesnt compile and as far as i can see doesn't work. Is there a newer zip file that contains the AwinDotnet files? I would like to see this working and/or develop this myself as I am about to undertake the same piece of work.... however.... this is incomplete.


joebourne wrote Mar 2, 2011 at 1:31 PM

Hi, thanks for the comment...
I just downloaded the zip, and yes, it does look a bit broken!

I know the code used to work, but to be honest ive not touched this code for years (literally!) i did it mainly as a proof of concept as at the time as there was nothing else that worked with the Visual Stuido... I never even used the resulting code for my own sites, and more recently ive moved away from ASP.NET and onto Google App Engine for my hobby programming.

Since i seem to be getting some interest in the project recently, i'll see if i can make some time over the next couple of weeks to fire up my old dev box and locate the code... lets just hope i still have the source! LOL.


HobedoGangsta wrote Mar 2, 2011 at 4:33 PM

I am/will be developing this into a quite sophisticated piece of interface.... as we need to create real time commissions report on our website. So i am very keen for this. I have just tried generating from the latest wsdl and it wont even compile.. so even if you pointed me in the direction of what you tweaked in the .cs file to make it work would be a very useful boost. thanks in hope that you have the code and/or can remember what you fixed in aw's broken wsdl interface

joebourne wrote Mar 3, 2011 at 9:38 AM

Not had a chance to dig out the original source code, but i did just try the new v3 WSDL and it worked fine for me with no need to make any modifications.
Simply open Visual Studio (im using 2010 pro), import the webreference from the AWIN site: http://v3.core.com.productserve.com/ProductServeService.wsdl

once you have the webrefeerence, you can call the methods:

Basic Example:
        ApiService a = new ApiService();

        a.UserAuthenticationValue = new UserAuthentication();            
        a.UserAuthenticationValue.sApiKey = "e53ce02f5XXXXXXXXXXXXXXX611adce8";

        getCategoryTree r = new getCategoryTree();
        r.iCategoryId = 0;            
        getCategoryTreeResponse result = a.getCategoryTree(r);
This worked fine for me - hover your mouse over "result" and you'll see its populated with all the various site categories...
When i get a chance i will update this project to use the new v3 api as the object model it presents makes life a lot simpler!

HobedoGangsta wrote Mar 4, 2011 at 10:06 AM

Thanks for that, and indeed the productservice seems to work. However, I am trying to get the commission, stats and impressions to work http://api.affiliatewindow.com/v3/AffiliateService?wsdl this doesnt appear to import or compile

Warning 1 Custom tool warning: Cannot import wsdl:portType
Detail: An exception was thrown while running a WSDL import extension: System.ServiceModel.Description.XmlSerializerMessageContractImporter
Error: Referenced type 'http://schemas.xmlsoap.org/soap/encoding/:Array' is only valid for encoded SOAP.
XPath to Error Source: //wsdl:definitions[@targetNamespace='http://api.affiliatewindow.com/']/wsdl:portType[@name='ApiPortType'] C:\dev2008\ems\ems\UpdateEmsAdmin\Service References\com.affiliateservice.com.core.v3\Reference.svcmap 1 1
So i presume its similar to problems you had in the past. So my question is what did you edit to make it work?
you can contact me on julian@e-tale.co.uk if you want to exchange directly ?
thanks for any help you can give on this

HobedoGangsta wrote Mar 10, 2011 at 12:55 PM

I have been complaining vociferously to affiliate window about the fact that their SOAP web services will only work with PHP due to the use of soap:enc attribute on children of the soap body. They have said "we are looking into it". In the mean time I am going to have to start hacking my own version without the benefit of the wsdl as i need to get my data asap.

Thanks for your comments and I hope you can get that code so i can see how you hacked the wsdl file to get it to work.

joebourne wrote Mar 10, 2011 at 1:58 PM

sent you an email... error you are reporting looks like its due to adding the WSDL as a "Service Reference" to a class library project. This error doesnt happen when adding the WSDL as a "Web Reference" to a Web project.... a 'feature' of Visual Studio i guess! :)

wrote Feb 13, 2013 at 7:36 PM