Hi,

sorry to bump up an old thread, but I am seeing the same problem as well with the webDialog while trying to add it to my controls collection. happens only when i have more than one instance of the same control.

System.ArgumentException: Invalid JSON primitive: ,|0|3,0,197px,26px,800px,530px,0||.
at System.Web.Script.Serialization.JavaScriptObjectDeserializer.BasicDeserialize(String input, Int32 depthLimit, JavaScriptSerializer serializer)
at System.Web.Script.Serialization.JavaScriptSerializer.Deserialize(JavaScriptSerializer serializer, String input, Type type, Int32 depthLimit)
at System.Web.Script.Serialization.JavaScriptSerializer.DeserializeObject(String input)
at Infragistics.Web.UI.Framework.RunBot.HandleOnInit(HttpContext context)
at Infragistics.Web.UI.Framework.ControlMain.OnInit(EventArgs e)
at System.Web.UI.Control.InitRecursive(Control namingContainer)
at System.Web.UI.Control.AddedControl(Control control, Int32 index)
at System.Web.UI.ControlCollection.Add(Control child)

Was a fix issued for this? thanks!

Hi John and ushatel,

I tried again to test samples with dialog, but I could not reproduce exception. I tested dialogs directly on page and wrapped into UpdatePanels. Tried various combinations of full and async postbacks in release and debug modes.
In order to help, I need a sample to reproduce. Please, write a simple sample, zip aspx/cs files and attach it within Options tabs. Or submit a report at link which I mentioned last time.

My machine has slightly different version of MicrosoftAjax.debug.js, though, I do not think that makes difference.
Under VisualStudio2008:
// Name:        MicrosoftAjax.debug.js
// Assembly:    System.Web.Extensions
// Version:     3.5.0.0
// FileVersion: 3.5.30729.5446

Under VisualStudio2010:
// Name:        MicrosoftAjax.debug.js
// Assembly:    System.Web.Extensions
// Version:     4.0.0.0
// FileVersion: 4.0.30319.17376

I tested following codes:

<form id="form1" runat="server">
 <asp:ScriptManager ID="ScriptManager1" runat="server"></asp:ScriptManager>
 <asp:UpdatePanel ID="UpdatePanel1" runat="server">
   <ContentTemplate>
    <ig:WebDialogWindow ID="WebDialogWindow1" runat="server" Width="300px" Height="200px">
     <ContentPane>
      <Template>
       <asp:Button ID="Button1" runat="server" Text="Button" />
       <asp:TextBox ID="TextBox1" runat="server"></asp:TextBox>
      </Template>
     </ContentPane>
    </ig:WebDialogWindow>
    <asp:Button ID="Button4" runat="server" Text="Button" />
   </ContentTemplate>
 </asp:UpdatePanel>
 <asp:UpdatePanel ID="UpdatePanel2" runat="server">
   <ContentTemplate>
    <ig:WebDialogWindow ID="WebDialogWindow2" runat="server" Width="300px" Height="200px">
     <ContentPane>
      <Template>
       <asp:Button ID="Button2" runat="server" Text="Button" />
       <asp:TextBox ID="TextBox2" runat="server"></asp:TextBox>
      </Template>
     </ContentPane>
    </ig:WebDialogWindow>
   </ContentTemplate>
 </asp:UpdatePanel>
 <asp:Button ID="Button3" runat="server" Text="Button" />
</form>

Hi Victor,

I should have added my script manager has an attribute "enablePartialRendering=false" . .could this have caused an issue?

I am working on reproducing this. If i am able to reproduce this, I will package it and send it across.

Thanks,
John

Victor,

I completely forgot to reply to this post. My mistake. Turned out this was a mistake in the javascript i was using to render my control that used a webdialogwindow.
Its been corrected and it works fine for me now.

Thanks a lot! 

Sorry bout the late reply. .This is strange because if i remove that exact same attribute it works just fine for me.
Anyways, i will work on replicating this sometime soon and we can then find out the exact cause.

THanks for teh estimated time.

Hi John,

If work around with theForm did not help, then there is probably some other issue in you application and service release will not help neither.
I need a sample.

I do not know exact date for next service release. I guess it will be in range of next 3-4 weeks.

and also for which versions of IG this service release (fix) will be applicable to. thanks!

Also, please do let me know in which service release this will be fixed.

Thanks Vik!