webservice call crash

See my comments in your other question.

This email carries a disclaimer, a copy of which may be read at http://learning.longhill.org.uk/disclaimer

I'm afraid that's my favorite bug:

https://bugs.launchpad.net/xibo/+bug/522861

Sorry to say that right now there is no good method to workaround it, even updating .net to 3.5 didn't helped in my installations. It's caused by some errors in .net - handling it correctly requires code reconstuction according to Dan's #2 post. Right now only restarting client fixes it...

http://social.msdn.microsoft.com/forums/en-US/windowsworkflowfoundation/thread/7ede9685-e632-4836-b32b-3ec9fbc9f54d/

Dan: What about if we store a global "GUID" in the client, initialised at first run and call the GetFile methods with that GUID per that article, then if hangup is detected switch to a new GUID. The return method from the async call could then check that the GUID returned is the current global one, and if it isn't, just ignore?

Is there mileage in that?

Alex

Hello,

I'm wondering if there will be some test version based on that suggestion (Alex's GUID research) in some near future?
As long as i'm not suffering problems fixed in 1.0.8 i could wait for some test instead of updating my 90 clients to 1.0.8 and then second time to new version :)
If no i'll update do 1.0.8 instead.

I haven't had any time to research Alex's suggestion as yet - I may get some time to look at it over the next 2 weeks. If I do I will update this bug and you can try them out.

We're currently tied up on some project work. There definitely won't be a 1.0.9 so any possible fix for this will be in 1.2.0-rc2 or 3. I'd have thought well be putting out rc2 at some point next week.

Alex

This email carries a disclaimer, a copy of which may be read at http://learning.longhill.org.uk/disclaimer

Dan - Thanks for info, there is no rush for me, i've just asked becouse updateing 90 clients that work without problem (we're not changing already started layouts) it pointless if there is chance for any better version on horizon :)

Alex - So there will be a 1.2.0 windows client? I thought 1.0.x is final windows version, and 1.2 would be a python someday :)
Anyway, version number is not important to me, i'm always download fresh source and compile it myself, becouse i need alt+f4 to be blocked and syslog trace listener compiled in to dump all debug logs centrally :)

Yep - there will be a .net 1.2.0 client which will have some modifications over the 1.0.8 client (specifically it will be date/time aware so the client can run complex schedules offline and will support running "Windowed" - ie not fullscreen at a given size and position). It may also support using PowerPoint Viewer rather than full Power Point - we had some code contributed for that but haven't reviewed it in detail yet.

Python client has ground to a halt at the moment. We have a Chinese dev Rino working on porting the Browsernode code over to Berkelium to get us a newer version of Chrome to embed and hopefully to improve performance - but we're not quite there yet. The windows client at the moment doesn't support some of the new gizmos - transparent background webpages, microblog search etc like the Python one does. It'll all become clearer when I get to writing the release notes for 1.2.0 (as it will detail all changes between 1.0.8 and 1.2.0 - ie alot!)

A

Thanks for detailed info :) Great to hear about storing shedule locally!
So now i'm sure that spending time in update to 1.0.8 in pointless for me.