Hello,

Please ensure that you have included ISNet.dll and ISNet.WebUI.dll in your project's bin folder.

Check your web.config under <assemblies>. You should remove ISNet and ISNet.WebUI assemblies from web.config. The Assemblies are like following:

<add assembly="ISNet.WebUI, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=B1F2A8511635667A"/>
<add assembly="ISNet, Version=3.0.5000.1, Culture=neutral, PublicKeyToken=B1F2A8511635667A"/>
<add assembly="ISNet.ActiveReports.Exporting, Version=5.0.7200.1, Culture=neutral, PublicKeyToken=B1F2A8511635667A"/>

Please remove the code above from web.config and try to deploy to your server.

Hope this helps.

Thank you.

Hello,

Yes, we would like to apologize for the incorrect information in the documentation. We will surely update the documentation for future reference.

When you display WebProgressBar, it will run on the FlyPostback. But you are still able to run WebProgressBar in FullPostback mode by using the Server-side event provided in its properties.

Hope this helps.

Thank you.

Hello,

You can change the hyperlink text using InitializeRow like following:

protected void WebGrid1_InitializeRow(object sender, ISNet.WebUI.WebGrid.RowEventArgs e)
{
   WebGrid1.RootTable.Columns.GetNamedItem("HyperlinkColumn").HyperlinkDisplayText = "Hyperlink Text";
}

Hope this helps.

Thank you.

Hello Frank,

To set location of WebDialogBox, you can use the following code in Client-side:

function DoShow()
{
   var dlgBox = ISGetObject("WebDialogBox1");
   dlgBox.ShowDialog();
   dlgBox.Window.MoveTo(300, 300);
}

Invoke DoShow() function using button or any controls.

To freeze the dialogbox, you can use OnCreated Client-side event in WebDialogBox and add the following code:

function Created()
{
   var el = document.getElementById("dvWnd_Global_wndWebDialogBox1");
   el.IsInteractiveObject = false;
}

Hope this helps.

Thank you.

Hello,

When you update the hotfix, did you update the WebUI.NET Framework assembly as well?

Try to download the latest hotfix for Framework and see how it goes when you apply the assembly in your production server.

If the error still persists, could you send me a simple working sample that replicates this issue? I will try to run the sample from my end and see the result.

Thank you.