Thread: WSI - Updated code samples?

Hey Guys,

We're trying to use some WSI tools we've developed against an ML 8.1.2 isntance and noticing we are getting errors. Mainly, we used to do the following:

AspDotNetStorefrontImportWebService svc = new AspDotNetStorefrontImportWebService();
private string _userName = ConfigurationManager.AppSettings["StoreUserName"];
private string _password = ConfigurationManager.AppSettings["StorePassword"];

svc.Url = ConfigurationManager.AppSettings["WSIUrl"];

svc.DoIt(blahblah);

Is this now AspDotNetStorefrontImportWebServiceSoapClient?

If so, any updated samples for these changes?

What errors are you getting? Is that all of the code or did you omit some of the non-critical parts? What is the blah-blah-blah that you are sending?

Sorry

The blah blah blah is;

svc.DoIt(_userName, _password, saveCats.ToString());

I can't even compile the code above. AspDotNetStorefrontImportWebService isn't even valid anymore.

The error I'm getting now is:

"System.Web.Services.Protocols.SoapHeaderException : Server unavailable, please try later ---> System.ApplicationException: WSE842: The service pipeline could not be created. ---> System.Configuration.ConfigurationErrorsException: WSE032: There was an error loading the microsoft.web.services3 configuration section. ---> System.Configuration.ConfigurationErrorsException: WSE040: Type AspDotNetStorefront.ASPDNSFUsernameTokenManager could not be loaded. Please check the configuration file. (D:\\Docs\\Visual Studio 2008\\Projects\\birdiesroom\\Web\\web.config line 201)\n at System.Configuration.BaseConfigurationRecord.Evalu ateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)\n at System.Configuration.BaseConfigurationRecord.Evalu ate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject)\n at System.Configuration.BaseConfigurationRecord.GetSe ctionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)\n at System.Configuration.BaseConfigurationRecord.GetSe ction(String configKey, Boolean getLkg, Boolean checkPermission)\n at System.Configuration.BaseConfigurationRecord.GetSe ction(String configKey)\n at System.Web.HttpContext.GetSection(String sectionName)\n at Microsoft.Web.Services3.Configuration.WebServicesC onfiguration.get_Current()\n --- End of inner exception stack trace ---\n at Microsoft.Web.Services3.Configuration.WebServicesC onfiguration.get_Current()\n at Microsoft.Web.Services3.Configuration.WebServicesC onfiguration.get_MessagingConfiguration()\n at Microsoft.Web.Services3.WseProtocol.ModifyInitiali zedExtensions(PriorityGroup group, SoapExtension[] extensions)\n at System.Web.Services.Protocols.SoapServerProtocol.I nitialize()\n --- End of inner exception stack trace ---\n --- End of inner exception stack trace ---"

If I go straight to the ipx.asmx address I am able to see it working, so I know it's there.

We've got these same tools working on instances of aspdnsf from 7.1 onward. There seems to have been a WSI update?

It's valid, but it has to be referenced in your solution that you are trying to compile. For example, if you build a new application and try to reference that it's going to fail. You need to add a web reference in order to use it and compile.

Also, read through this knowledgebase article

Knowledgebase article was spot on.

Funny, this is a fresh 8.1.2 download and it didn't have the define wse3 line.

And we now have to do the following to use WSI:

AspDotNetStorefrontImportWebServiceSoapClient svc = new AspDotNetStorefrontImportWebServiceSoapClient();
private string _userName = ConfigurationManager.AppSettings["StoreUserName"];
private string _password = ConfigurationManager.AppSettings["StorePassword"];

svc.Endpoint.Address = new EndpointAddress(ConfigurationManager.AppSettings["WSIUrl"]);

string response = svc.DoIt(_userName, _password, saveCats.ToString());

I took the WSI samples from the documentation, updated the reference to this instance of ML 8.1.2 and AspDotNetStorefrontImportWebService is no longer valid...only AspDotNetStorefrontImportWebServiceSoapClient .