Greg,
You can also put this in the config file on the server side and see if
you get a file generated. If so there will more than likely be some
info in there for you.
Warning it does generate a lot of data quickly.
system.diagnostics
trace autoflush=true /
sources
source
Neil, Wallace, I created an ASP.NET client (instead of SL4) and attempted to
upload 7MB and I get this stack of exceptions:
♦ CommunicationException: An error occurred while receiving the HTTP response
to http://localhost/service/Aggregation.svc. This could be due to the
service endpoint
[mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Tuesday, 20 September 2011 12:58 PM
To: 'ozDotNet'
Subject: How to diagnose WCF 'NotFound'
Folks, I have a WCF service hosted in IIS that is called by an SL4 app to send
client files to the server. Years ago I updated various
Add a WCF error handler behaviour which changes the http return code to 200
even if there is an error (on the server side).
I've seen a few samples where people do this trick. However, I would rather
have a naked wrestling match with a rabid grizzly bear than write some WCF
behaviour code.
Now I know what WCF really stands for. Wrestling Championship Federation.
Have you seen my bear, Tibbers? :)
On Wed, Sep 21, 2011 at 8:01 AM, Greg Keogh g...@mira.net wrote:
Add a WCF error handler behaviour which changes the http return code to
200 even if there is an error (on the server
Ye I think this whole naked bear wrestling thing is a wonderful idea.
Perhaps @ the next TechEd or CodeCamp Greg could do something like this. I
for one would pay good money to see it :)
On 21 September 2011 10:52, Stephen Price step...@littlevoices.com wrote:
Now I know what WCF really stands
Thanks Jake, I'll save that code sample. The reason I was so hostile to the
idea of writing behaviours comes from last year where I thought I had to
write one to allow an SL4 app to send authentication data with each WCF
call. I wanted to use the equivalent of a SOAP header which was really easy
Folks, I have a WCF service hosted in IIS that is called by an SL4 app to
send client files to the server. Years ago I updated various configuration
values to allow up to 20MB transfer. This is on the server side:
binding name=Bind1 maxBufferSize=20971520
maxReceivedMessageSize=20971520
believe there is a way of sending a Stream that can be read in chunks
and allow progress reporting. Is that right? Anyone done it?
Yep, define this contract
|[ServiceContract]
public interface ISoftwareUpdater
{
[OperationContract()]
*Stream*GetDownloadStream(FileUpdate fileUpdate);
