title: What problems will I face if I force the use of keywords like "public" and "private" in ASP.NET MVC Area names?
body: <p>I'd like to name one of my APS.NET MVC 4.0 Areas "Public". When I add a new Area and names it "Public" Visual Studio instead gives me the name "_Public" - obviously protecting me from using a C# keyword for the Area. The name would be used both in the namespace and as a part of the class name of <code>PublicController</code>. I'd prefer that my public-facing URL didn't contain any underscores, so I've done a rename back to "Public" and so far it seems to work just fine - my Index-page is rendering fine.</p>
  
  <p>Is there any reason I shouldn't go with "Public" without the underscore as the area name? What problems will I face in the future, if any?</p>