mike's web log

var grid = new WebGrid(source: selectedData, rowsPerPage: 3);

<form method="post">
  <div>
    <label for="searchGenre">Genre to look for:</label>
    <input type="text" name="searchGenre" value="" />
    <input type="Submit" value="Search Genre" /><br/>
    (Leave blank to list all movies.)<br/>
    </div>
</form>

@{
    var db = Database.Open("WebPagesMovies") ;
    var selectCommand = "SELECT * FROM Movies";
    var searchTerm = "";

    if(IsPost && !Request.QueryString["searchGenre"].IsEmpty() ) { 
        selectCommand = "SELECT * FROM Movies WHERE Genre = @0";
        searchTerm = Request.QueryString["searchGenre"];
    }

    var selectedData = db.Query(selectCommand, searchTerm);
    var grid = new WebGrid(source: selectedData, rowsPerPage:3);
}

<form method="get">
  <!-- etc -->
</form>

if(!Request.QueryString["searchGenre"].IsEmpty() ) { // etc }

<select>
  <option value="1">One</option>
  <option value="2" selected >Two</option>
  <option value="3">Three</option>
</select>

< select name="NumberList">
  <option 
   selected=@(Request.Form["NumberList"] == "1")
   value="1">One</option>
  <option 
    selected=@(Request.Form["NumberList"] == "2")                
    value="2">Two</option>
  <option 
    selected=@(Request.Form["NumberList"] == "3")
    value="3">Three</option>                    
</select>

When you use membership security in ASP.NET Web Pages Razor, you can limit access to pages so that only logged-in users can see those pages. One way to do that, as explained before, is to add a test like the following to the top of a page (or to the _PageStart.cshtml page in the protected folder):

@{
    if (!WebSecurity.IsAuthenticated) {
        Response.Redirect("~/Login");
    }
}

If the user isn't logged in, they're redirected to the Login page (in this case, in the site's root).

Nice, but then the user still has to find their way back to the page they originally wanted. Ideally, after the user has logged in, you send them back to the original page automatically. And because they're now logged in, the gatekeeper code lets them through.

The usual way to approach this is to include a return URL address when you redirect to the login page. You can add it as a query-string value to the login URL. Then in the login page, once the user has logged in ok, you can get that return URL and jump back.

Here's an updated version of the code from above with some logic to create a return URL:

if (!WebSecurity.IsAuthenticated) {
     Response.Redirect("~/Login?returnUrl=" + Request.Url.LocalPath);
}

http://localhost/members/info.cshtml

The Request.Url.LocalPath property returns this:

/members/info.cshtml

So the URL of the redirect to the Login page looks like this:

http://localhost/Login?returnUrl=/members/info.cshtml

The login page can then return to the original page using logic like this:

if(IsPost){
    var username = Request.Form["username"];
    var password = Request.Form["password"];
    bool rememberMe = Request.Form["rememberMe"].AsBool();

    // Various kinds of validations and checks for user 
    // existence here, then ...

    if (WebSecurity.Login(username, password, rememberMe)) {
        if(!Request.QueryString["returnUrl"].IsEmpty()){
            Context.RedirectLocal(Request.QueryString["returnUrl"]);
        }
        else{
            Response.Redirect("~/"); // Goes to site home
        }
    }
}

Update (2018 Jul 29)  Someone has noted in the comments that in ASP.NET MVC (.NET Core 2.0+), RedirectLocal is a method on the base page, not on HttpContext, as it was when I wrote this. See the docs.

Notice that the redirection back to the original page is done with the Context.RedirectLocal method. You could use Response.Redirect. But Context.RedirectLocal makes sure that redirection is performed only if the return URL is local to the site. This helps prevent someone from hacking in a complete URL that would redirect to an external site in order to try to snatch authentication tokens or what have you.

If you happen to be using the Starter Site template in WebMatrix (v2 Beta or later), the login page already has this built in. In any page that you create where you want to let the user log in and then return, make sure you add a query string when you invoke the login page, and set returnUrl to the local path of the current page, as illustrated above.

Page.Title = "My Page";

PageData["Title"] = "My Page";

<title>@Page.Title</title>

<title>@PageData["Title"]</title>

Page.Me = "Mike";

<p>@PageData["me"]</p>

Page.MyCount = "3";
if(Page.MyCount.IsInt()){
    // Fail with compiler error. 
}

<select name="selectGenre">
   @foreach(var row in db.Query("Select DISTINCT Genre FROM Movies ORDER BY Genre")){
      <option 
          selected=@(row.Genre==Request.Form["selectGenre"])>
          @row.Genre
      </option>
   }
</select>

• Conditional attributes. Described earlier.
  
  
• Validation.GetHtml has been changed to Validation.For. This method renders the goo that's used to hook client-side validation. See earlier.
  
  
• The ~ operator is now recognized in HTML markup, so you don't need to use Href any more to resolve it. See earlier. I think this is my favorite feature, actually, even tho some might consider it comparatively small, dunno.
  
  
• The Scripts helper was renamed to Assets (aka the Assets Manager), and the method names were tweaked. If you were using Scripts to register scripts or .css files, you have to change those references.

@grid.GetHtml(
    columns: grid.Columns(
        grid.Column(format: @<a href="~/EditMovie?id=@item.ID">Edit</a>),
        grid.Column("Title"),
        grid.Column("Year")
  )
)

<input type="checkbox" name="check1" value="check1" checked />
<input type="checkbox" name="check1" value="check1" checked="true" />
<input type="checkbox" name="check1" value="check1" checked="anyThingAtAll" />

<select>
   <option value="A">A</option>
   <option value="B" selected>B</option>
   <option value="C">C</option>
 </select>

<input type="text" name="text1" value="@Request.Form["text1"]" />

<input type="checkbox" name="check1" value="check1"
   @if(Request.QueryString["val1"] == "true"){
       <text>checked="checked"</text>
   }
/>

<input type="checkbox" name="check1" value="check1" 
    @(Request.QueryString["val1"] == "true" ? Html.Raw("checked=\"checked\"") : null)
/>

@{
    bool check1 = false;
    if(Request.QueryString["val1"] == "true"){
        check1=true;
    }
}

<input type="checkbox" name="check1" value="check1" checked="@check1" />

<input type="checkbox" name="check1" value="check1" 
    checked=@(!(Request.QueryString["val1"].IsEmpty())) />

@{
    bool checked1=false;
    bool checked2=false;
    Object someObject = null;
    string aString = String.Empty;

    if(Request.QueryString["val1"] == "true"){
        checked1=true;  
    }

    if(Request.QueryString["val2"] == "true"){
        checked2=true;
        someObject = this;
        aString="Hello, conditional attributes!";
    }
}
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="utf-8" />
  <title>Test Conditional Attributes</title>
</head>
<body>

<form method="post">
    
<div>
  <input type="checkbox" name="check1" value="check1" checked="@checked1"  /> 
      Value 1
  <br/>
  <input type="checkbox" name="check2" value="check2" checked="@checked2" /> 
      Value 2
  <br/>
  <input type="checkbox" name="check3" value="check3" checked="@someObject" /> 
      Some object
  <br/>
  <input type="checkbox" name="check4" value="check4" checked="@Request.Form["name"]" />
      Request.Form["name"]
  <br/>
  <input type="checkbox" name="check5" value="check5" checked="@aString" /> 
      aString
</div>

<div>
  <input type="submit" name="buttonSubmit" value="Submit" />
</div>
</form>
</body>
</html>

• input-validation-error
  
• field-validation-error
  
• validation-summary-errors
  
• field-validation-valid
  
• input-validation-valid
  
• validation-summary-valid

<style>
   .validation-summary-errors{
      border:2px solid red; 
      color:red; 
      font-weight:bold;
      padding:10px;
      margin:10px;
      width:30%}
   
   .field-validation-error{
      color:red; 
      font-weight:bold; 
      background-color:yellow;}
   
   .input-validation-error{
      color:red; 
      font-weight:bold; 
      background-color:pink;}
</style>

Formatting Client-Side Validation Errors

<input type="text"
    name="coursename"
    value=@Request.Form["coursename"]
    @Validation.For("coursename")  @Validation.ClassFor("coursename")  />
@Html.ValidationMessage("coursename", "<=")

Static and Dynamic Error Display

@if(IsPost && !Validation.IsValid()){ 
    <text>@Html.ValidationSummary("Please fix the marked errors") </text>
}

• Updated validation in Web Pages v2 Basics of adding validation in v2 (server-side only)
  
• Updated validation in Web Pages v2, Part 2 (adding client-side validation)