ASP Web Pages WebGrid
Inspect a real legacy WebGrid without fetching a production table.
How it works
WebGrid is a legacy System.Web.Helpers HTML table helper with sorting and paging conventions. This bounded example supplies three in-memory rows and disables automatic sorting and paging to make its exact rendering predictable. It demonstrates the actual helper, not a hand-written table labelled WebGrid.
Use the separate Windows lab
This is a legacy-maintenance course. Classic ASP uses IIS and VBScript; ASP.NET Web Pages uses .NET Framework and Razor. Neither runs in PHP, Apache or Bhylu’s browser playground. The reviewed baseline is 32-bit IIS Express 10.0.2001, .NET Framework 4.8, Web Pages / Razor 3.2.9 and the Windows VBScript engine. ADO database examples use the actual 32-bit Jet OLE DB 4.0 provider, not SQL Server or XAMPP MySQL.
Download download-lab.mjs into a separate empty learning folder. Run node download-lab.mjs to fetch hash-checked source files into a new bhylu-asp-lab folder, then cd bhylu-asp-lab and node run-lab.mjs --start. Before deployment, local preview uses node download-lab.mjs http://127.0.0.1:8000/examples/asp/. The source downloader refuses an existing destination. Review its source before running it.
The foreground launcher needs your own 32-bit IIS Express installation with Classic ASP, .NET Framework 4.8 and the VBScript engine available. It downloads the three pinned Web Pages packages from NuGet into its private cache, binds only localhost on port 8142 and stops when you press Ctrl+C. Keep its console open. Visit http://localhost:8142/webpages-webgrid.cshtml. It does not install IIS, enable Windows features, change Apache/PHP/MySQL, or publish any files. See the bundled README.txt for manual setup and test boundaries.
Each complete Classic ASP source requires the supplied Global.asa acknowledgement; Web Pages uses _PageStart.cshtml. Database and file examples create owned temporary files only under this private lab’s blocked App_Data folder. Sources are public text downloads; do not upload them as executable teaching endpoints on Bhylu.
Example
@using System.Web.Helpers
@{
Layout = null;
var rows = new[] { new { Name="Mending", Seats=3 }, new { Name="Patchwork", Seats=0 }, new { Name="Buttons", Seats=2 } };
var grid = new WebGrid(rows, canPage:false, canSort:false);
}
<div id="result">@grid.GetHtml(columns:grid.Columns(grid.Column("Name"), grid.Column("Seats")))</div>
Focus on the lesson operations
This excerpt omits shared lab setup. Use the complete download and supporting files to run it.
@using System.Web.Helpers
@{
Layout = null;
var rows = new[] { new { Name="Mending", Seats=3 }, new { Name="Patchwork", Seats=0 }, new { Name="Buttons", Seats=2 } };
var grid = new WebGrid(rows, canPage:false, canSort:false);
}
<div id="result">@grid.GetHtml(columns:grid.Columns(grid.Column("Name"), grid.Column("Seats")))</div>
Expected result
Name Seats Mending 3 Patchwork 0 Buttons 2
The helper produces real table headings and rows, checked in a browser. The underlying fixture remains three objects. For large datasets, server-side paging needs a separate bounded query, count and stable ordering policy.