This is a stab at building a (very ugly and rudimentary) database-backed Web application using the .NET SDK, in an effort to learn about the limitations and pain points.
The main question I have is should we ship it in its current form (or, I guess, at all). In particular, I broke it out into a bunch of per-page modules, which is very unnatural for .NET. This was originally to take advantage of Spin routing, which was probably not worth it; but it turned out that some pages were not amenable to Wizerisation, and having separate modules meant I could at least Wizerise those where it worked.
There's a bunch of utility stuff that's emerged from this which might be helpful for people, but is insufficiently baked to go into the core SDK. In particular what I really want is to bridge more from the WASI objects to .NET idioms (e.g. HttpContext and the ASP.NET service model, or IDbConnection and IDataReader), but that's likely to be a long game and involve significant wrestling.
This is a stab at building a (very ugly and rudimentary) database-backed Web application using the .NET SDK, in an effort to learn about the limitations and pain points.
The main question I have is should we ship it in its current form (or, I guess, at all). In particular, I broke it out into a bunch of per-page modules, which is very unnatural for .NET. This was originally to take advantage of Spin routing, which was probably not worth it; but it turned out that some pages were not amenable to Wizerisation, and having separate modules meant I could at least Wizerise those where it worked.
There's a bunch of utility stuff that's emerged from this which might be helpful for people, but is insufficiently baked to go into the core SDK. In particular what I really want is to bridge more from the WASI objects to .NET idioms (e.g. HttpContext and the ASP.NET service model, or IDbConnection and IDataReader), but that's likely to be a long game and involve significant wrestling.
How do we want to proceed?