Thanks for the help everyone,
I finally tracked it down to a bad web.config file and missing rights
on the upload acc. the web.config file had an html commented line in
it removing the commented line and I could query the
lists.asmx file, uploading was a matter of adding the upload account
int
In the case of 1), I'd think you could also add a say,
.GregsPreferredFormatString property & associated instance var to store it in,
couldn't you?
Could you do likewise with extension methods? (That's what I'd do in ruby...)
Cheers,
-Roy
-Original Message-
From: Discussion of advanc
I'm dealing with a piece of legacy software that does automated HTTP
Posts for Customer Integrations. I've looked through the source code
and found that it has no mechanism for adding the "SOAPAction" Http
Header. I was wondering if anyone knows if this Header can somehow be
passed through the UR
Legacy software sending XML to your web service and because it's not sending
the SOAPAction header it's receiving an error from the server?
Add this attribute to your web service:
[System.Web.Services.Protocols.SoapDocumentService(
RoutingStyle=SoapServiceRoutingStyle.RequestElement )]
This impos
Adam,
I don't think I explained myself very well. I don't control the web
service, and the software that sends the data to that web service is
the legacy piece I'm talking about. I was wondering if I could
construct a Soap Envelope that could embed the SOAPAction inside of
it. I know there is a
If the webservice is running under .NET 1.1, you're out of luck. You only
have SOAPAction HTTP header or RoutingStyle of RequestElement. In SOAP 1.1
SOAPAction was mandatory.
[Looking at the System.Web.Services code:]
If the webservice is running under .NET 2.0, and is written for SOAP 1.1,
you're
