I've just started using this cassini to support a local web service that deals with local printers (which is why I needed Cassini - I couldnt do this in IIS, I'm just not smart enough!)

I regularly encounter long amounts of time (15-20 seconds) from the time my app sends its web service til cassini "starts up" my web service.

I dont know how to better measure whats going on - I DO have the "keep app in memory" flag set for my bundled service in cassini.
Any ideas as to why I might have long times for web service start up ????
Also - how can I produce more log output for cassini?? ( this may help me some if I can get it to produce something more than cassini started!)

Thanks!

Hi, Derek.

We are not familiar with this particular issue. In order to better understand the problem, could you please confirm following:
We understand that you encounter a delay only on the first request sent to the web service, while subsequent requests get executed quickly. Is it correct?
And we understand you determined that delay happens in Cassini itself, not in your code. Is this correct too?

Unfortunately there is no additional logging in Cassini - what you see in the event log is all it has.

Regards,
UltiDev Team.

Thanks, Derek. It's a good info.

To better isolate the place where delay happens, please run your web service under Cassini while debugging it in Visual Studio. That will let you put the breakpoint in the web service and roughly measure the delay between the button click that invokes the web service, and the moment when debugger hits the breakpoint. That will give us clear indication whether the Cassini the cause of the delay. Please note that under debugger your web service will be running on different port (which you can specify as on of the parameters of the command-line Cassini process) so you will have to adjust the URL at your web service client for debugging purposes.

Best regards,
UltiDev Team.