mike's web log

<ul>
@foreach (var item in collection)
{
    <li>@item</li>
}
</ul>

It sounds like if I have lots of logic inside the loop, I might be best served moving that to the back end somewhere and just calling a method that returns the text to display within each list item.

@MyHelpers.HorizontalMenu(
    "Home|Default.cshtml", 
    "About|About.cshtml", 
    "Login|Login.cshtml", 
    "Register|Register.cshtml")
<h1>My Page</h1>
      <p>Hello, horizontal menu.</p>

@helper HorizontalMenu(params string[] menuListArrary) {

string[] menuItem;
string menulink = "";
string menuLIitems = "";

<style>
  /* This should all be in a .css somewhere */
  #horizontalMenu{height:28px;background-color:lightgray;
      font-family:"Segoe UI";font-size:11pt;font-weight:bold;
      color:white;}
  #horizontalMenu ul {margin:0px; padding:0px;}
  #horizontalMenu ul li{
    display:inline;height:30px;float:left;list-style:none;
      margin-left:15px;position:relative;
      border-right:2px solid white;padding:6px;
  }
  #horizontalMenu li a {color:#fff; text-decoration:none;}
  #horizontalMenu li a:hover {color:red;}    
</style>

     <div id="horizontalMenu">
        @for(int i = 0; i < menuListArrary.Length; i++){
          menulink = "";
          if(menuListArrary[i].Contains("|")){
            menuItem = menuListArrary[i].Split( new Char[]{'|'});
            menulink = 
                String.Format("<a href=\"{1}\">{0}</a>", 
                    menuItem[0], 
                    menuItem[1]);
          }
          else{
            menulink = menuListArrary[i];
          }
          menuLIitems += "<li>" + menulink + "</li>";
      }
      <ul>@Html.Raw(menuLIitems)</ul>  
      </div>
}

• The name of the file (MyHelpers.cshtml) acts as the namespace for any helpers in that file; the name of the helper itself (first list of the previous example) is the method. That's why the earlier example invokes the helper as MyHelpers.HorizontalMenu.
  


• The CSS for the menu layout probably should not be in this file; it probably should be in a separate .css file.
  


• And/or at least parts of the CSS should probably be parameterized so that you can pass values to it when you invoke the menu. Maybe.
  


• You can pass as many items to this as you like (hence the use of the params string[] syntax in the helper method signature).
  


• The original poster had noted that in some browsers, if the <ul> and <li> elements are on separate lines, the silly browser puts blank spaces between them. So a goal here was to smush everything together onto one line.
  


• The menu text and menu target/link are separated by a pipe character ("|"). This was a quick-and-dirty thing. It might be more elegant to pass, say, 2-element arrays to the helper or something, but I generally think that invoking helpers in a page should be as straightforward as possible.
  


• As coded, the links for the menu items have to be absolute. However, they really should be expressed, or at least expressable, using the ASP.NET ~ operator, which returns the virtual root, but which requires the ASP.NET Href method to resolve. I didn't bother.
  


• For some reason I thought it was important to have logic in case a menu item was passed to the helper that didn't have a target in it. I can't offhand think of when this would ever be useful, tho.

Disabling Request Validation

• ASP.NET Web Forms
  
• ASP.NET MVC
  
• ASP.NET Web Pages

Disabling Request Validation in ASP.NET Web Forms (4.0 or later)

<system.web>
  <httpRuntime requestValidationMode="2.0" />
</system.web>

<location path="test.aspx">
  <system.web>
    <httpRuntime requestValidationMode="2.0" />
  </system.web>
</location>

<configuration>
  <system.web>
    <pages validateRequest="false" />
  </system.web>
</configuration>

<@ Page validateRequest="false" %>

Disabling Request Validation in ASP.NET MVC

<system.web>
  <httpRuntime requestValidationMode="2.0" />
</system.web>

[HttpPost]
[ValidateInput(false)]
public ActionResult Edit(string comment) 
{
    if (ModelState.IsValid) 
    {
        //  Etc.
    }
    return View(comment);
}

[AllowHtml]
public string Prop1 { get;  set; }

var rawComment = Request.Unvalidated().Form["comment"];

Disabling Request Validation in ASP.NET Web Pages

// Validated, throws error if input includes markup
var userComment = Request.Form["userInput"]; 

Request.Unvalidated("userInput"); // Validation bypassed
Request.Unvalidated().Form["userInput"]; // Validation bypassed

Request.QueryString["userPreference"]; // Validated
Request.Unvalidated().QueryString["userPreference"]; // Validation bypassed;

Manually Checking Requests

// Encode the string input
StringBuilder sb = new StringBuilder(
    HttpUtility.HtmlEncode(htmlInputTxt.Text));
// Selectively allow <b> and <i>
sb.Replace("&<b&>", "<b>");
sb.Replace("&</b&>", "</b>");
sb.Replace("&<i&>", "<i>");
sb.Replace("&</i&>", "</i>");

See Also

• Ending Insurance Company Abuses.
  
• Keeping Premiums Low.
  
• Expanding Access To Care.
  
• Closing the Medicare Prescription Drug "Donut Hole."

• Equal Pay For Equal Work.
  
• Improving Women's Health.
  
• Protecting Women's Right to Choose.

• Job Creation.
  
• Saved the auto industry from collapse.
  
• The private sector has created jobs.

... my pet peeves. They’re about pronunciation, rather than grammar and news people on television are doing this more every day:

1. Fill, instead of feel.
2. Pill, instead of peel.
[etc.]

To me, this “sims” just lazy. [source]

Plural forms are always going to be determined by what the majority is used to or comfortable with, with a tendency towards laziness. Very few people are going to bother with Priora when Priuses is perfectly functional. However, that doesn't mean that words adopted into English should use regular plural forms; it simply means that they are likely to. [source]

If I'm talking with friends or sending a text, I don't use "proper" English grammar, but I do recognize that my grammar is incorrect. I just don't care, and I know that my listener will understand me even if I'm lazy. [source]

A split infinitive can be a lazy way not to write a better sentence. [source]

When a speaker or writer uses incorrect subject/verb agreement, it tells the audience that he is either lazy or does not care. [source]

Using the singular 'they' means you're not trying, you don't know grammar rules, or you're lazy. [source]

• Deploying to a Hosting Provider
  
• Intro to ASP.NET MVC 3

• Authors help develop their "brand".
  
• Readers can learn to associate an author's name with a specific level, quality, and focus of work.
  
• Content will get a personality and human face.
  
• Readers get the (correct) impression that documentation is created by actual people.
  
• Writers get public acknowledgment of their work — the company in effect puts its own stamp of approval on the writer's work, by name.