Search Results

Search found 5 results on 1 pages for 'cyrix86'.

Page 1/1 | 1 

  • Sharepoint listsService.updateList method clarification

    - by cyrix86
    I've seen an example here: msdn but it's a little confusing. So if I have a list definition with a field called "CustomField" and I want to update the "ShowField" attribute of this field to be true then I would do this: XmlNode listNode = listService.GetList("MyList"); string version = listNode.Attributes["Version"].Value; string guid = listNode.Attributes["Name"].Value; XmlDocument xmlDoc = new XmlDocument(); XmlElement updateFields = xmlDoc.CreateElement("Fields"); string fieldXml = @"<Method ID="1"><Field Name="CustomField" ShowField="true" /></Method>"; updateFields.InnerXml = fieldXml; XmlNode result = listService.UpdateList(guid, null, null, updateFields, null, version); I'm confused because it would seem that you would need to provide a field element to indicate what field to update and then a value element to specify the new value. Could someone clarify this please?

    Read the article

  • Ajax call to WCF service returns 12031 ERROR_INTERNET_CONNECTION_RESET on new endpoint

    - by cyrix86
    I have extended a WCF service with new functionality in the form of a second service contract. The service.cs now implements both contracts. I have added another endpoint to expose the new contract operations. Here is my web.config relating to the service <system.serviceModel> <bindings> <basicHttpBinding> <binding name="BasicHttpBinding" /> </basicHttpBinding> <webHttpBinding> <binding name="XmlHttpBinding"/> </webHttpBinding> </bindings> <services> <service name="MyNamespace.MyService" behaviorConfiguration="MyServiceBehavior"> <!-- Service Endpoints --> <endpoint address="xmlHttp1" behaviorConfiguration="XmlHttpBehavior" binding="webHttpBinding" bindingConfiguration="XmlHttpBinding" contract="MyNamespace.IContract1" /> <endpoint address="xmlHttp2" binding="webHttpBinding" behaviorConfiguration="XmlHttpBehavior" bindingConfiguration="XmlHttpBinding" contract="MyNamespace.IContract2" /> <endpoint address="" binding="basicHttpBinding" bindingConfiguration="BasicHttpBinding" contract="MyNamespace.IContract1" /> </service> </services> <behaviors> <serviceBehaviors> <behavior name="MyServiceBehavior"> <!-- To avoid disclosing metadata information, set the value below to false and remove the metadata endpoint above before deployment --> <serviceMetadata httpGetEnabled="true"/> <!-- To receive exception details in faults for debugging purposes, set the value below to true. Set to false before deployment to avoid disclosing exception information --> <serviceDebug includeExceptionDetailInFaults="false"/> </behavior> </serviceBehaviors> <endpointBehaviors> <behavior name="XmlHttpBehavior"> <webHttp/> </behavior> </endpointBehaviors> </behaviors> </system.serviceModel> From Javascript, calling 'http://server/wcfServiceApp/MyService.svc/xmlHttp1/Method1' still works fine. Calling 'http://server/wcfServiceApp/MyService.svc/xmlHttp2/Method2' returns the 12031 error. There must be something simple I'm not doing, any help is appreciated.

    Read the article

  • Windows Sidebar gadget - cannont access a div in Flyout DOM

    - by cyrix86
    In the main gadget html, there is a div with an onclick that calls this method in the Gadget script file: ShowFlyout = function() { System.Gadget.Flyout.show = true; var flyoutDoc = System.Gadget.Flyout.document; var mainFlyoutDiv = flyoutDoc.getElementById('divFlyout'); mainFlyoutDiv.innerHTML = "hello"; } Here is the Flyout html: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html> <head> <title>This is a flyout</title> <link href="Css\FlyoutStyle.css" type="text/css" rel="Stylesheet" /> </head> <body> <div id="divFlyout" > </div> </body> </html> The problem is that mainFlyoutDiv is always null. When peering into the System.Gadget.Flyout.document object through the debugger, the body parameter is null - I don't think that's right. The System.Gadget.Flyout.file value is being set elsewhere when the gadget first loads. What am I doing wrong? Also, does the System.Gadget.Flyout.show property have to be true before the System.Gadget.Flyout.document property can be accessed? My ultimate goal is to open a flyout and dynamically populate it's html

    Read the article

1