Your reported problem is already queued in the dev-team work items. However, it hasn't been processed further due to the release of 2016 R1 priorities and urgency.

I will keep you informed when the nightly build is available and ready to be evaluated.

Hi Yudi, now the error 500.23 disappeared...

Glad to know that after configure the handlers and modules declaration in web.config file, the site now works on IIS 8.5 and Integrated Pipeline mode. Error 500.23 no longer persist.

... but I'm getting the following errors/problems:

MS IE 11 - see the attachment screenshot shown from the debbuger

I suspect that you might use older version of WebGrid and WebUI.NET Framework 3.0. I recommend you to apply latest build of WebGrid 9 and WebUI.NET Framework 3.0 in order to resolve the problem on IE 11 browser.

If the issue still persist after apply latest build of WebGrid 9 and WebUI.NET Framework 3.0, please feel free to let me know.

Firefox 43.xx - the filter icons aren't displayed, only dots .... instead.

I tried to reproduce the reported problem by rendering the live sample of Filtering.aspx in Firefox 43.0.2 with no luck. The filter icon displayed without any problems.

Please ensure that you have applied latest build of WebGrid 9 and WebUI.NET Framework 3.0 and let me know the result.

Moreover, using WebGrid designer I got the error: Intersoft componet Editor for VS 2012 is either not installed or corrupted. ...

Try to remove ISNet.WebUI.WebGrid.Editor.dll and ISNet.WebUI.WebGrid.Editor.Metro.dll from GAC, then update ISNet.WebUI.WebGrid.Editor.dll and ISNet.WebUI.WebGrid.Editor.Metro.dll (%programfiles(x86)%\Intersoft Solutions\WebUI Studio for ASP.NET\WebUI.NET Framework 3.0\Bin) in GAC. You can use gacutil command to do this. Please check the detail command in here.

When a new HTTP project is created in Vista or Windows 2008 Operating System (or newer), the default application pool is using DefaultAppPool, which uses IIS 7.0 (or newer) Integrated .NET pipeline mode. Intersoft’s components use several HttpHandlers for managing resources and chart engine. This article guides you to migrate the existing application configuration file to take advantage of the IIS 7.0 (or newer) Integrated pipeline mode.

Should the problem persist after follow the method to add the configuration, please send us your web.config file so that I can assist you further.

In order to set a percentage height, its parent element must have an explicit height. So the parent (container) of WebGrid, in this case is the div element, must have an explicit height property. That height can also be percentage, that just moves the problem up to the next level. This means the parent's parent (grand-parent) height must be defined too. This could go until the html root element.

So set the height of the html and the body element to 100%, as well as every single ancestor element of that element that you wish to have the 100% height in the first place.

Add following style tag into the page, Webcomboexpbasic.aspx:

<style type="text/css">
    html, body, form
    {
        height: 100%;
        width: 100%;
        padding: 0;
        margin: 0;
    }
</style>

Next, set the grid's parent height to specific height, for example 100%.

<div style="height: 100%;">
    <ISWebGrid:WebGrid ID="WebGrid1" runat="server"
        DefaultStyleMode="Elegant" UseDefaultStyle="True" 
        Height="50%" Width="98%" ...> 
        ...
    </ISWebGrid:WebGrid>
</div>

It's all set. The height issue no longer persist and the message "There are no rows in this view." appear in the correct position.

This should helps.

...

 on a client, we would access that property like this:

wgGetCellByName(SelectedRow,"EmployeeId").EmployeeName;

and that worked in IE8 and below, however it doesn't work in HTML5 browsers. With the new DOCTYPE html, in new browsers, that gets rendered as a direct property on a combo object, while in older browsers it's rendered as a member of attributes array on a combo object in js.

...

I recommend you to switch your JS code to the new client-side API of WebGrid. In order to get value from hidden column using HiddenDataMember, you can use following snippet code:

function GetValueFromHiddenColumnUsingHiddenDataMember()
{
    // get the client object reference of WebGrid1
    var grid = ISGetObject("WebGrid1");

    // get the row object of the selected object
    var rowObj = grid.GetSelectedObject().GetRowObject();

    // get cells of the row object
    var cells = rowObj.GetCells();

    // get EmployeeId cell
    var employee = cells.GetNamedItem("EmployeeId");


    var employeeName = customer.GetElement().attributes["EmployeeName"].value;

    alert(employeeName);
}

Have you encountered this issue and is there some solutio to it?

I can reproduce the problem when using wgGetCellByName. The problem no longer persist when the recent client-side API is used.

This should helps.