Windows Desktop/Sidebar Gadget with Recording Schedule

[cncb]

Are you doing what this article outlines for calling a .Net web service from JS?

I was not setting the 'Content-Type' in the request header and it sounded like that might be the problem based on the article but unfortunately I still get the same error even when setting that appropriately. Would it be easy to append this XML data onto the end of 'InfoXML.aspx' (which I'm already reading) or would that be a pain?

[UncleJohnsBand]

I was not setting the 'Content-Type' in the request header and it sounded like that might be the problem based on the article but unfortunately I still get the same error even when setting that appropriately. Would it be easy to append this XML data onto the end of 'InfoXML.aspx' (which I'm already reading) or would that be a pain?

Learned that accessing web services via Javascript is inconsistent between browsers and because of Javascript security accessing web services outside of the host domain doesn't work.....so I took you lead and updated the services/infoxml.aspx page to handle the service call and write the result out in the reponse. To invoke just use infoxml.aspx?gadget=true and you will get the xml object for the pending and in-progress recordings.....leave off the parm and you get what you always did.

Cheers

[UncleJohnsBand]

Learned that accessing web services via Javascript is inconsistent between browsers and because of Javascript security accessing web services outside of the host domain doesn't work.....so I took you lead and updated the services/infoxml.aspx page to handle the service call and write the result out in the reponse. To invoke just use infoxml.aspx?gadget=true and you will get the xml object for the pending and in-progress recordings.....leave off the parm and you get what you always did.

Cheers

Ok...attached is the patch...just follow instructions above using the querystring ?gadget=true to get the pending and in-progress events.

[cncb]

I'm not sure if some of my files might be out-of-sync due to previous patches but I'm getting the following error when trying to use the parameter:

Code:

Invalid URI: The format of the URI could not be determined.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.UriFormatException: Invalid URI: The format of the URI could not be determined.

Source Error:


Line 44:                 string URI = (String) Session["HostURI"];
Line 45:                 string url = URI + "/public/services/manageservice.asmx";
Line 46:                 mng.Url = url;
Line 47:                 string gadget = mng.getGadgetFeed();
Line 48:


Source File: c:\Users\Public\NPVR\web\public\services\InfoXML.aspx.cs    Line: 46

[UncleJohnsBand]

I'm not sure if some of my files might be out-of-sync due to previous patches but I'm getting the following error when trying to use the parameter:

Code:

Invalid URI: The format of the URI could not be determined.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.UriFormatException: Invalid URI: The format of the URI could not be determined.

Source Error:


Line 44:                 string URI = (String) Session["HostURI"];
Line 45:                 string url = URI + "/public/services/manageservice.asmx";
Line 46:                 mng.Url = url;
Line 47:                 string gadget = mng.getGadgetFeed();
Line 48:


Source File: c:\Users\Public\NPVR\web\public\services\InfoXML.aspx.cs    Line: 46

Ok...I think I know what it is......when trying to access it via NEWA.....go to a secured page first then go to the infoxml.aspx page.....let me know what happens then. I think I may be setting that session variable in the login pages.....so if you went straight to infoxml.aspx without hitting login page first you would get this error. Patch posted.....

[cncb]

Ok...I think I know what it is......when trying to access it via NEWA.....go to a secured page first then go to the infoxml.aspx page.....let me know what happens then. I think I may be setting that session variable in the login pages.....so if you went straight to infoxml.aspx without hitting login page first you would get this error. Patch posted.....

Sorry, I'm still getting an error (different one, see below). However, if I do go to the NEWA home page (where I am logged in) and then try to access infoxml.aspx with the parameter it is successful so I think you are right on the money with your assessment.

Code:

An existing connection was forcibly closed by the remote host
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Source Error:


Line 386:        [System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://tempuri.org/getGadgetFeed", RequestNamespace="http://tempuri.org/", ResponseNamespace="http://tempuri.org/", Use=System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)]
Line 387:        public string getGadgetFeed() {
Line 388:            object[] results = this.Invoke("getGadgetFeed", new object[0]);
Line 389:            return ((string)(results[0]));
Line 390:        }


Source File: c:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\0a635572\38fd2de4\App_WebReferences.0cy53_9h.0.cs    Line: 388

[UncleJohnsBand]

Sorry, I'm still getting an error (different one, see below). However, if I do go to the NEWA home page (where I am logged in) and then try to access infoxml.aspx with the parameter it is successful so I think you are right on the money with your assessment.

Code:

An existing connection was forcibly closed by the remote host
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

Source Error:


Line 386:        [System.Web.Services.Protocols.SoapDocumentMethodAttribute("http://tempuri.org/getGadgetFeed", RequestNamespace="http://tempuri.org/", ResponseNamespace="http://tempuri.org/", Use=System.Web.Services.Description.SoapBindingUse.Literal, ParameterStyle=System.Web.Services.Protocols.SoapParameterStyle.Wrapped)]
Line 387:        public string getGadgetFeed() {
Line 388:            object[] results = this.Invoke("getGadgetFeed", new object[0]);
Line 389:            return ((string)(results[0]));
Line 390:        }


Source File: c:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\0a635572\38fd2de4\App_WebReferences.0cy53_9h.0.cs    Line: 388

Found problem....use this patch file.

[cncb]

Found problem....use this patch file.

Success! Thanks for all your work on this.

[cncb]

Success!

I spoke a little too soon. For some reason javascript doesn't like the XML returned by this (no document element). The XML text looks valid to me. The only difference I see between this and the regular infoxml is that this is UTF-16-encoded compared to UTF-8. I'm not sure if this is causing the problem but could you possibly switch it to UTF-8? Thanks.

[UncleJohnsBand]

I spoke a little too soon. For some reason javascript doesn't like the XML returned by this (no document element). The XML text looks valid to me. The only difference I see between this and the regular infoxml is that this is UTF-16-encoded compared to UTF-8. I'm not sure if this is causing the problem but could you possibly switch it to UTF-8? Thanks.

Ok..attached patch now outputs the xml document in utf-8 encoding.

For web services you pass the doucment as a string and .Net holds strings as utf-16 so I had to take the response from the webservice (which is a string) load it to an xmldocument and than save that to the http response set to utf-8 encoding....seems to be working fine.

Let me know if it works.