Not sure how many of you read my first post on my thoughts on Oxite. Well, here's my offering on trying to make things a little closer to MVC by offering my perspective on the code. Please note that I want to keep these simple refactorings as conversational as possible, so if you see something that offends or upsets you with my interpretation/implementation, PLEASE COMMENT. :) Let's examine the SignIn action under the AccountController: [AcceptVerbs(HttpVerbs.Post)]
public ActionResult SignIn(string username, string password, bool rememberMe, string returnUrl)
{
PageTitle.AdditionalPageTitleSegments = new string[] { "Sign In" };
...
This past weekend some discussion sprung up around a new blog engine called Oxite. This blog engine is put out by the MIX Online team and it's used to power their blog. Now, I'm not going to rehash some of the statements made by other members of the community since there is no point in beating a dead horse. However, if you want check them out I suggest that first see Rob Conery's thoughts on Oxite as well as Scott Koon with TLC for Oxite post. The thing I do want to point out is that the team...