Examining the Edit Methods and Edit View

旧城等待， 2022-10-10 04:55 161阅读 0赞

In this section, you'll examine the generated action methods and views for the movie controller. Then you'll add a custom search page.

Run the application and browse to the `Movies` controller by appending */Movies* to the URL in the address bar of your browser. Hold the mouse pointer over an **Edit** link to see the URL that it links to.

[![EditLink\_sm][EditLink_sm]][EditLink_sm_EditLink_sm]

The **Edit** link was generated by the `Html.ActionLink` method in the *Views\\Movies\\Index.cshtml* view:

@Html.ActionLink("Edit", "Edit", new { id=item.ID })

[![Html.ActionLink][]][Html.ActionLink 1]

The `Html` object is a helper that's exposed using a property on the `WebViewPage` base class. The `ActionLink`method of the helper makes it easy to dynamically generate HTML hyperlinks that link to action methods on controllers. The first argument to the `ActionLink` method is the link text to render (for example, `<a>Edit Me</a>`). The second argument is the name of the action method to invoke. The final argument is an [ anonymous object][anonymous object] that generates the route data (in this case, the ID of 4).

The generated link shown in the previous image is *http://localhost:xxxxx/Movies/Edit/4*. The default route takes the URL pattern `{controller}/{action}/{id}`. Therefore, ASP.NET translates *http://localhost:xxxxx/Movies/Edit/4* into a request to the `Edit` action method of the `Movies`controller with the parameter `ID` equal to 4.

You can also pass action method parameters using a query string. For example, the URL *http://localhost:xxxxx/Movies/Edit?ID=4* also passes the parameter `ID` of 4 to the `Edit` action method of the `Movies` controller.

[![EditQueryString][]][EditQueryString 1]

Open the `Movies` controller. The two `Edit` action methods are shown below.

//
    // GET: /Movies/Edit/5
    
    public ActionResult Edit(int id) 
    {
       
        Movie movie = db.Movies.Find(id);
        return View(movie);
    }
    
    //
    // POST: /Movies/Edit/5
    
    [HttpPost]
    public ActionResult Edit(Movie movie) 
    {
       
        if (ModelState.IsValid) 
        {
       
            db.Entry(movie).State = EntityState.Modified;
            db.SaveChanges();
            return RedirectToAction("Index");
        }
        return View(movie);
    }

Notice the second `Edit` action method is preceded by the `HttpPost` attribute. This attribute specifies that that overload of the `Edit` method can be invoked only for POST requests. You could apply the `HttpGet` attribute to the first edit method, but that's not necessary because it's the default. (We'll refer to action methods that are implicitly assigned the `HttpGet` attribute as `HttpGet` methods.)

The `HttpGet` `Edit` method takes the movie ID parameter, looks up the movie using the Entity Framework `Find` method, and returns the selected movie to the Edit view. When the scaffolding system created the Edit view, it examined the `Movie` class and created code to render `<label>` and `<input>` elements for each property of the class. The following example shows the Edit view that was generated:

@model MvcMovie.Models.Movie
    
    @{
        ViewBag.Title = "Edit";
    }
    
    <h2>Edit</h2>
    
    <script src="@Url.Content("~/Scripts/jquery.validate.min.js")" type="text/javascript"></script>
    <script src="@Url.Content("~/Scripts/jquery.validate.unobtrusive.min.js")" type="text/javascript"></script>
    
    @using (Html.BeginForm()) {
        @Html.ValidationSummary(true)
        <fieldset>
            <legend>Movie</legend>
    
            @Html.HiddenFor(model => model.ID)
    
            <div class="editor-label">
                @Html.LabelFor(model => model.Title)
            </div>
            <div class="editor-field">
                @Html.EditorFor(model => model.Title)
                @Html.ValidationMessageFor(model => model.Title)
            </div>
    
            <div class="editor-label">
                @Html.LabelFor(model => model.ReleaseDate)
            </div>
            <div class="editor-field">
                @Html.EditorFor(model => model.ReleaseDate)
                @Html.ValidationMessageFor(model => model.ReleaseDate)
            </div>
    
            <div class="editor-label">
                @Html.LabelFor(model => model.Genre)
            </div>
            <div class="editor-field">
                @Html.EditorFor(model => model.Genre)
                @Html.ValidationMessageFor(model => model.Genre)
            </div>
    
            <div class="editor-label">
                @Html.LabelFor(model => model.Price)
            </div>
            <div class="editor-field">
                @Html.EditorFor(model => model.Price)
                @Html.ValidationMessageFor(model => model.Price)
            </div>
    
            <p>
                <input type="submit" value="Save" />
            </p>
        </fieldset>
    }
    
    <div>
        @Html.ActionLink("Back to List", "Index")
    </div>

Notice how the view template has a `@model MvcMovie.Models.Movie` statement at the top of the file — this specifies that the view expects the model for the view template to be of type `Movie`.

The scaffolded code uses several *helper methods* to streamline the HTML markup. The [ `Html.LabelFor`][_Html.LabelFor] helper displays the name of the field ("Title", "ReleaseDate", "Genre", or "Price"). The [ `Html.EditorFor`][_Html.EditorFor] helper displays an HTML `<input>` element. The [ `Html.ValidationMessageFor`][_Html.ValidationMessageFor] helper displays any validation messages associated with that property.

Run the application and navigate to the */Movies* URL. Click an  **Edit** link. In the browser, view the source for the page. The HTML in the page looks like the following example. (The menu markup was excluded for clarity.)

<!DOCTYPE html>
    <html>
    <head>
        <meta charset="utf-8" />
        <title>Edit</title>
        <link href="/Content/Site.css" rel="stylesheet" type="text/css" />
        <script src="/Scripts/jquery-1.5.1.min.js" type="text/javascript"></script>
        <script src="/Scripts/modernizr-1.7.min.js" type="text/javascript"></script>
    </head>
    <body>
        <div class="page">
            <header>
                <div id="title">
                    <h1>MVC Movie App</h1>
                </div>
               ...
            </header>
            <section id="main">
                
    
    <h2>Edit</h2>
    
    <script src="/Scripts/jquery.validate.min.js" type="text/javascript"></script>
    <script src="/Scripts/jquery.validate.unobtrusive.min.js" type="text/javascript"></script>
    
    <form action="/Movies/Edit/4" method="post">    <fieldset>
            <legend>Movie</legend>
    
            <input data-val="true" data-val-number="The field ID must be a number." 
    		data-val-required="The ID field is required." id="ID" name="ID" type="hidden" value="4" />
    
            <div class="editor-label">
                <label for="Title">Title</label>
            </div>
            <div class="editor-field">
                <input class="text-box single-line" id="Title" name="Title" type="text" value="Rio Bravo" />
                <span class="field-validation-valid" data-valmsg-for="Title" data-valmsg-replace="true"></span>
            </div>
    
            <div class="editor-label">
                <label for="ReleaseDate">ReleaseDate</label>
            </div>
            <div class="editor-field">
                <input class="text-box single-line" data-val="true" data-val-required="The ReleaseDate field is required." 
    		id="ReleaseDate" name="ReleaseDate" type="text" value="4/15/1959 12:00:00 AM" />
                <span class="field-validation-valid" data-valmsg-for="ReleaseDate" data-valmsg-replace="true"></span>
            </div>
    
            <div class="editor-label">
                <label for="Genre">Genre</label>
            </div>
            <div class="editor-field">
                <input class="text-box single-line" id="Genre" name="Genre" type="text" value="Western" />
                <span class="field-validation-valid" data-valmsg-for="Genre" data-valmsg-replace="true"></span>
            </div>
    
            <div class="editor-label">
                <label for="Price">Price</label>
            </div>
            <div class="editor-field">
                <input class="text-box single-line" data-val="true" data-val-number="The field Price must be a number." 
    		data-val-required="The Price field is required." id="Price" name="Price" type="text" value="9.99" />
                <span class="field-validation-valid" data-valmsg-for="Price" data-valmsg-replace="true"></span>
            </div>
    
            <p>
                <input type="submit" value="Save" />
            </p>
        </fieldset>
    </form>
    <div>
        <a href="/Movies">Back to List</a>
    </div>
    
            </section>
            <footer>
            </footer>
        </div>
    </body>
    </html>

The `<input>` elements are in an HTML `<form>` element whose `action` attribute is set to post to the */Movies/Edit* URL. The form data will be posted to the server when the **Edit** button is clicked.

## Processing the POST Request ##

The following listing shows the `HttpPost` version of the `Edit` action method.

[HttpPost]
    public ActionResult Edit(Movie movie) 
    {
       
        if (ModelState.IsValid) 
        {
       
            db.Entry(movie).State = EntityState.Modified;
            db.SaveChanges();
            return RedirectToAction("Index");
        }
        return View(movie);
    }

The ASP.NET framework model binder takes the posted form values and creates a `Movie` object that's passed as the `movie` parameter. The `ModelState.IsValid` check in the code verifies that the data submitted in the form can be used to modify a `Movie` object. If the data is valid, the code saves the movie data to the `Movies` collection of the `MovieDBContext` instance. The code then saves the new movie data to the database by calling the `SaveChanges` method of `MovieDBContext`, which persists changes to the database. After saving the data, the code redirects the user to the `Index` action method of the `MoviesController` class, which causes the updated movie to be displayed in the listing of movies.

If the posted values aren't valid, they are redisplayed in the form. The `Html.ValidationMessageFor` helpers in the *Edit.cshtml* view template take care of displaying appropriate error messages.

[![abcNotValid][]][abcNotValid 1]

**Note about locales**   If you normally work with a locale other than English, see [ Supporting ASP.NET MVC 3 Validation with Non-English Locales.][Supporting ASP.NET MVC 3 Validation with Non-English Locales.]

## Making the Edit Method More Robust ##

The `HttpGet` `Edit` method generated by the scaffolding system doesn't check that the ID that's passed to it is valid. If a user removes the ID segment from the URL (*http://localhost:xxxxx/Movies/Edit*), the following error is displayed:

[![Null\_ID][Null_ID]][Null_ID_Null_ID]

A user could also pass an ID that doesn't exist in the database, such as *http://localhost:xxxxx/Movies/Edit/1234*. You can make two changes to the `HttpGet` `Edit` action method to address this limitation. First, change the `ID` parameter to have a default value of zero when an ID isn't explicitly passed. You can also check that the `Find` method actually found a movie before returning the movie object to the view template. The updated `Edit` method is shown below.

public ActionResult Edit(int id = 0)
    {
       
        Movie movie = db.Movies.Find(id);
        if (movie == null)
        {
       
            return HttpNotFound();
        }
        return View(movie);
    }

If no movie is found, the `HttpNotFound` method is called.

All the `HttpGet` methods follow a similar pattern. They get a movie object (or list of objects, in the case of `Index`), and pass the model to the view. The `Create` method passes an empty movie object to the Create view. All the methods that create, edit, delete, or otherwise modify data do so in the `HttpPost` overload of the method. Modifying data in an HTTP GET method is a security risk, as described in the blog post entry [ ASP.NET MVC Tip \#46 – Don’t use Delete Links because they create Security Holes][ASP.NET MVC Tip _46 _ Don_t use Delete Links because they create Security Holes]. Modifying data in a GET method also violates HTTP best practices and the architectural REST pattern, which specifies that GET requests should not change the state of your application. In other words, performing a GET operation should be a safe operation that has no side effects.

## Adding a Search Method and Search View ##

In this section you'll add a `SearchIndex` action method that lets you search movies by genre or name. This will be available using the */Movies/SearchIndex* URL. The request will display an HTML form that contains input elements that a user can fill in in order to search for a movie. When a user submits the form, the action method will get the search values posted by the user and use the values to search the database.

## Displaying the SearchIndex Form ##

Start by adding a `SearchIndex` action method to the existing `MoviesController` class. The method will return a view that contains an HTML form. Here's the code:

public ActionResult SearchIndex(string searchString)
    {
                 
        var movies = from m in db.Movies
                     select m;
    
        if (!String.IsNullOrEmpty(searchString))
        {
       
            movies = movies.Where(s => s.Title.Contains(searchString));
        }
    
        return View(movies);
    }

The first line of the `SearchIndex` method creates the following [ LINQ][LINQ] query to select the movies:

var movies = from m in db.Movies
                     select m;

The query is defined at this point, but hasn't yet been run against the data store.

If the `searchString` parameter contains a string, the movies query is modified to filter on the value of the search string, using the following code:

if (!String.IsNullOrEmpty(searchString))
        {
       
            movies = movies.Where(s => s.Title.Contains(searchString));
        }

LINQ queries are not executed when they are defined or when they are modified by calling a method such as `Where`or `OrderBy`. Instead, query execution is deferred, which means that the evaluation of an expression is delayed until its realized value is actually iterated over or the [`ToList`][ToList] method is called. In the `SearchIndex` sample, the query is executed in the SearchIndex view. For more information about deferred query execution, see [Query Execution][].

Now you can implement the `SearchIndex` view that will display the form to the user. Right-click inside the `SearchIndex` method and then click **Add View**. In the  **Add View** dialog box, specify that you're going to pass a `Movie` object to the view template as its model class. In the **Scaffold template** list, choose **List**, then click **Add**.

[![AddSearchView][]][AddSearchView 1]

When you click the **Add** button, the *Views\\Movies\\SearchIndex.cshtml* view template is created. Because you selected **List** in the **Scaffold template** list, Visual Web Developer automatically generated (scaffolded) some default content in the view. The scaffolding created an HTML form. It examined the `Movie` class and created code to render `<label>` elements for each property of the class. The listing below shows the Create view that was generated:

@model IEnumerable<MvcMovie.Models.Movie>
    
    @{
        ViewBag.Title = "SearchIndex";
    }
    
    <h2>SearchIndex</h2>
    
    <p>
        @Html.ActionLink("Create New", "Create")
    </p>
    <table>
        <tr>
            <th>
                Title
            </th>
            <th>
                ReleaseDate
            </th>
            <th>
                Genre
            </th>
            <th>
                Price
            </th>
            <th></th>
        </tr>
    
    @foreach (var item in Model) {
        <tr>
            <td>
                @Html.DisplayFor(modelItem => item.Title)
            </td>
            <td>
                @Html.DisplayFor(modelItem => item.ReleaseDate)
            </td>
            <td>
                @Html.DisplayFor(modelItem => item.Genre)
            </td>
            <td>
                @Html.DisplayFor(modelItem => item.Price)
            </td>
            <td>
                @Html.ActionLink("Edit", "Edit", new { id=item.ID }) |
                @Html.ActionLink("Details", "Details", new { id=item.ID }) |
                @Html.ActionLink("Delete", "Delete", new { id=item.ID })
            </td>
        </tr>
    }
    
    </table>

Run the application and navigate to */Movies/SearchIndex*. Append a query string such as `?searchString=ghost` to the URL. The filtered movies are displayed.

[![SearchQryStr][]][SearchQryStr 1]

If you change the signature of the `SearchIndex` method to have a parameter named `id`, the `id` parameter will match the `{id}` placeholder for the default routes set in the *Global.asax* file.

{
       controller}/{
       action}/{
       id}

The modified `SearchIndex` method would look as follows:

public ActionResult SearchIndex(string id)
    {
       
        string searchString = id;
        var movies = from m in db.Movies
                     select m;
    
        if (!String.IsNullOrEmpty(searchString))
        {
       
            movies = movies.Where(s => s.Title.Contains(searchString));
        }
    
        return View(movies);
    }

You can now pass the search title as route data (a URL segment) instead of as a query string value.

[![SearchRouteData][]][SearchRouteData 1]

However, you can't expect users to modify the URL every time they want to search for a movie. So now you you'll add UI to help them filter movies. If you changed the signature of the `SearchIndex` method to test how to pass the route-bound ID parameter, change it back so that your `SearchIndex` method takes a string parameter named `searchString`:

public ActionResult SearchIndex(string searchString)
    {
                 
         var movies = from m in db.Movies
                      select m;
    
        if (!String.IsNullOrEmpty(searchString))
        {
       
            movies = movies.Where(s => s.Title.Contains(searchString));
        }
    
        return View(movies);
    }

Open the *Views\\Movies\\SearchIndex.cshtml* file, and just after `@Html.ActionLink("Create New", "Create")`, add the following:

@using (Html.BeginForm()){   
             <p> Title: @Html.TextBox("SearchString") 
             <input type="submit" value="Filter" /></p>
            }

The following example shows a portion of the *Views\\Movies\\SearchIndex.cshtml* file with the added filtering markup.

@model IEnumerable<MvcMovie.Models.Movie>
    
    @{
        ViewBag.Title = "SearchIndex";
    }
    
    <h2>SearchIndex</h2>
    
    <p>
        @Html.ActionLink("Create New", "Create")
        
         @using (Html.BeginForm()){   
             <p> Title: @Html.TextBox("SearchString") <br />  
             <input type="submit" value="Filter" /></p>
            }
    </p>

The `Html.BeginForm` helper creates an opening `<form>` tag. The `Html.BeginForm` helper causes the form to post to itself when the user submits the form by clicking the **Filter** button.

Run the application and try searching for a movie.

[![SearchIndxIE9\_title][SearchIndxIE9_title]][SearchIndxIE9_title_SearchIndxIE9_title]

There's no `HttpPost` overload of the `SearchIndex` method. You don't need it, because the method isn't changing the state of the application, just filtering data.

You could add the following `HttpPost SearchIndex`method. In that case, the action invoker would match the `HttpPost SearchIndex` method, and the `HttpPost SearchIndex` method would run as shown in the image below.

[HttpPost]
    public string SearchIndex(FormCollection fc, string searchString)
    {
       
        return "<h3> From [HttpPost]SearchIndex: " + searchString + "</h3>";
    }

[![SearchPostGhost][]][SearchPostGhost 1]

However, even if you add this `HttpPost`version of the `SearchIndex`method, there's a limitation in how this has all been implemented. Imagine that you want to bookmark a particular search or you want to send a link to friends that they can click in order to see the same filtered list of movies. Notice that the URL for the HTTP POST request is the same as the URL for the GET request (localhost:xxxxx/Movies/SearchIndex) -- there's no search information in the URL itself. Right now, the search string information is sent to the server as a form field value. This means you can't capture that search information to bookmark or send to friends in a URL.

The solution is to use an overload of `BeginForm`that specifies that the POST request should add the search information to the URL and that is should be routed to the HttpGet version of the `SearchIndex`method. Replace the existing parameterless `BeginForm`method with the following:

@using (Html.BeginForm("SearchIndex","Movies",FormMethod.Get))

[![BeginFormPost\_SM][BeginFormPost_SM]][BeginFormPost_SM_BeginFormPost_SM]

Now when you submit a search, the URL contains a search query string. Searching will also go to the`HttpGet SearchIndex` action method, even if you have a`HttpPost SearchIndex` method.

[![SearchIndexWithGetURL][]][SearchIndexWithGetURL 1]

## Adding Search by Genre ##

If you added the `HttpPost` version of the `SearchIndex` method, delete it now.

Next, you'll add a feature to let users search for movies by genre. Replace the `SearchIndex` method with the following code:

public ActionResult SearchIndex(string movieGenre, string searchString)
    {
       
        var GenreLst = new List<string>();
    
        var GenreQry = from d in db.Movies
                       orderby d.Genre
                       select d.Genre;
        GenreLst.AddRange(GenreQry.Distinct());
        ViewBag.movieGenre = new SelectList(GenreLst);
    
        var movies = from m in db.Movies
                     select m;
    
        if (!String.IsNullOrEmpty(searchString))
        {
       
            movies = movies.Where(s => s.Title.Contains(searchString));
        }
    
        if (string.IsNullOrEmpty(movieGenre))
            return View(movies);
        else
        {
       
            return View(movies.Where(x => x.Genre == movieGenre));
        }
    
    }

This version of the `SearchIndex` method takes an additional parameter, namely `movieGenre`. The first few lines of code create a `List` object to hold movie genres from the database.

The following code is a LINQ query that retrieves all the genres from the database.

var GenreQry = from d in db.Movies
                       orderby d.Genre
                       select d.Genre;

The code uses the `AddRange` method of the generic `List` collection to add all the distinct genres to the list. (Without the `Distinct` modifier, duplicate genres would be added — for example, comedy would be added twice in our sample). The code then stores the list of genres in the `ViewBag` object.

The following code shows how to check the `movieGenre` parameter. If it's not empty the code further constrains the movies query to limit the selected movies to the specified genre.

if (string.IsNullOrEmpty(movieGenre))
            return View(movies);
        else
        {
       
            return View(movies.Where(x => x.Genre == movieGenre));
        }

## Adding Markup to the SearchIndex View to Support Search by Genre ##

Add an `Html.DropDownList` helper to the *Views\\Movies\\SearchIndex.cshtml* file, just before the `TextBox` helper. The completed markup is shown below:

<p>
        @Html.ActionLink("Create New", "Create")
        @using (Html.BeginForm()){   
             <p>Genre: @Html.DropDownList("movieGenre", "All")  
               Title: @Html.TextBox("SearchString")  
             <input type="submit" value="Filter" /></p>
            }
    </p>

Run the application and browse to */Movies/SearchIndex*. Try a search by genre, by movie name, and by both criteria.

In this section you examined the CRUD action methods and views generated by the framework. You created a search action method and view that let users search by movie title and genre. In the next section, you'll look at how to add a property to the `Movie` model and how to add an initializer that will automatically create a test database.

[EditLink_sm]: http://i2.asp.net/media/2578522/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_EditLink_sm_10958d0e-da03-46f0-9656-5937da4aca7c.png?cdn_id=2013-08-19-002
[EditLink_sm_EditLink_sm]: http://i2.asp.net/media/2578516/WindowsLiveWriter_AddingaCreateMethodandCreateView_F8FB_EditLink_thumb.png?cdn_id=2013-08-19-002
[Html.ActionLink]: http://i1.asp.net/media/2578534/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_Html.ActionLink_thumb.png?cdn_id=2013-08-19-002
[Html.ActionLink 1]: http://i1.asp.net/media/2578528/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_Html.ActionLink_2.png?cdn_id=2013-08-19-002
[anonymous object]: http://weblogs.asp.net/scottgu/archive/2007/05/15/new-orcas-language-feature-anonymous-types.aspx
[EditQueryString]: http://i2.asp.net/media/2578546/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_EditQueryString_thumb.png?cdn_id=2013-08-19-002
[EditQueryString 1]: http://i2.asp.net/media/2578540/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_EditQueryString.png?cdn_id=2013-08-19-002
[_Html.LabelFor]: http://msdn.microsoft.com/en-us/library/gg401864%28VS.98%29.aspx
[_Html.EditorFor]: http://msdn.microsoft.com/en-us/library/system.web.mvc.html.editorextensions.editorfor%28VS.98%29.aspx
[_Html.ValidationMessageFor]: http://msdn.microsoft.com/en-us/library/system.web.mvc.html.validationextensions.validationmessagefor%28VS.98%29.aspx
[abcNotValid]: http://i3.asp.net/media/2578558/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_abcNotValid_thumb.png?cdn_id=2013-08-19-002
[abcNotValid 1]: http://i2.asp.net/media/2578552/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_abcNotValid.png?cdn_id=2013-08-19-002
[Supporting ASP.NET MVC 3 Validation with Non-English Locales.]: http://msdn.microsoft.com/en-us/library/gg674880%28VS.98%29.aspx
[Null_ID]: http://i1.asp.net/media/2578570/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_Null_ID_thumb.png?cdn_id=2013-08-19-002
[Null_ID_Null_ID]: http://i3.asp.net/media/2578564/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_Null_ID_2.png?cdn_id=2013-08-19-002
[ASP.NET MVC Tip _46 _ Don_t use Delete Links because they create Security Holes]: http://stephenwalther.com/blog/archive/2009/01/21/asp.net-mvc-tip-46-ndash-donrsquot-use-delete-links-because.aspx
[LINQ]: http://msdn.microsoft.com/en-us/library/bb397926.aspx
[ToList]: http://msdn.microsoft.com/en-us/library/bb342261.aspx
[Query Execution]: http://msdn.microsoft.com/en-us/library/bb738633.aspx
[AddSearchView]: http://i3.asp.net/media/2578582/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_AddSearchView_thumb.png?cdn_id=2013-08-19-002
[AddSearchView 1]: http://i3.asp.net/media/2578576/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_AddSearchView_2.png?cdn_id=2013-08-19-002
[SearchQryStr]: http://i1.asp.net/media/2578594/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_SearchQryStr_thumb.png?cdn_id=2013-08-19-002
[SearchQryStr 1]: http://i2.asp.net/media/2578588/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_SearchQryStr_2.png?cdn_id=2013-08-19-002
[SearchRouteData]: http://i1.asp.net/media/2578606/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_SearchRouteData_thumb.png?cdn_id=2013-08-19-002
[SearchRouteData 1]: http://i1.asp.net/media/2578600/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_SearchRouteData_2.png?cdn_id=2013-08-19-002
[SearchIndxIE9_title]: http://i2.asp.net/media/2578618/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_SearchIndxIE9_title_thumb.png?cdn_id=2013-08-19-002
[SearchIndxIE9_title_SearchIndxIE9_title]: http://i1.asp.net/media/2578612/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_SearchIndxIE9_title_2.png?cdn_id=2013-08-19-002
[SearchPostGhost]: http://i3.asp.net/media/2578630/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_SearchPostGhost_thumb.png?cdn_id=2013-08-19-002
[SearchPostGhost 1]: http://i3.asp.net/media/2578624/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_SearchPostGhost.png?cdn_id=2013-08-19-002
[BeginFormPost_SM]: http://i1.asp.net/media/2578642/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_BeginFormPost_SM_thumb.png?cdn_id=2013-08-19-002
[BeginFormPost_SM_BeginFormPost_SM]: http://i1.asp.net/media/2578636/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_BeginFormPost_SM_2.png?cdn_id=2013-08-19-002
[SearchIndexWithGetURL]: http://i3.asp.net/media/2578654/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_SearchIndexWithGetURL_thumb.png?cdn_id=2013-08-19-002
[SearchIndexWithGetURL 1]: http://i3.asp.net/media/2578648/Windows-Live-Writer_Examining-the-Edit-Methods-and-Edit-View_E344_SearchIndexWithGetURL_2.png?cdn_id=2013-08-19-002