Web

Since writing yesterday’s post about what annoys me regarding the limited insight most web developers have in regards to Routing vs Rewriting. It occurred to me that I might be able to make the difference and benefits between the two more clear, after remembering a post Phil Haack wrote about Editable MVC Routes. By taking my companies already production ready URL Rewriter that supports runtime-editing of rewriter rules and adding support for routes. I would essentially be merging together Routing and Rewriting in the same configuration, and making the routes just as editable as the rewriter rules. By doing this, my hope is that it should illustrate the benefits of having both a Rewriter as well as a Router in your web arsenal, because you can play with both in real time and start to connect in your mind when one is more useful than the other. ...

I recorded the following presentation for DevReady.NET, a new project that I am working on with a bunch of talented MVC’s and Microsoft employees. After I get done with editing the presentation, I will post it up to DevReady.NET and my blog. This will be my first try at making a video presentation for the web, so I look forward to your comments.

A question that I have been hearing a lot lately is: How do I change the view location in MVC? But what they really mean to say is: How do I create a new ViewEngine that uses the view locations of my choosing? It is actually very simple to do, and once you see it, I think you will agree with my assessment. The first thing we are going to do to create our custom ViewEngine, is define the paths that we want to use for our master pages, view pages, and shared pages. I have taken the liberty to define the following paths, you can customize them however you wish: ...

In this economy you have to do everything to keep your skills fresh and current so that employers find you a desirable hire. I really though the tips provided in 8 Ways to Recession-Proof Your Programming Career where spot on when this article came out last year. And now that the TechRepublic has released 10 kills developers will need in the next 5 years. I have decided to give you some of my favorite Wrox books that align very well to this TechRepublic article. ...

It was just announced at MIX09 that ASP.NET MVC 1.0 has been released for general use and is out of the Release Candidate phase. There has been no word on the changes form RC 2 to this release version. But I will keep this post updated as I learn more. Also as of writing this the download hasn’t been posted to CodePlex either, but I am sure that it will be posted pretty soon. ...

Phil Haack has announced the availability of ASP.NET MVC 1.0 Release Candidate 2. You can download the new version from Microsoft. Source code and samples are also available on the ASP.NET CodePlex workspace. Overall, this new version doesn’t have many changes in the area of development and tooling, but there has been improvement for deploying ASP.NET MVC applications. The setup process now requires .NET 3.5 SP1 to be installed, where in the past it was optional because the additional assemblies where included with the install. ...

If you are getting something like the following error message in ASP.NET MVC: A potentially dangerous Request.Form value was detected from the client (Description="some HTML text") This is because of something called Request Validation, that is a feature put in place to protect your application cross site scripting attacks, as described in a White Paper on ASP.NET: Many sites are not aware that they are open to simple script injection attacks. Whether the purpose of these attacks is to deface the site by displaying HTML, or to potentially execute client script to redirect the user to a hacker’s site, script injection attacks are a problem that Web developers must contend with. Script injection attacks are a concern of all web developers, whether they are using ASP.NET, ASP, or other web development technologies. The ASP.NET request validation feature proactively prevents these attacks by not allowing unencoded HTML content to be processed by the server unless the developer decides to allow that content. ...

This is a continuation of my Introduction to ASP.NET MVC series. As I outlined before this is in an effort to write the book and keep blogging, I decided to write/blog the last chapter, Chapter 2. I am doing this so I can receive feedback on this chapter as early as possible. Because this chapter, in my opinion, is probably the most critical of the book, it defines the context around ASP.NET MVC and how it differs from ASP.NET Web Forms, as well as giving a historical perspective of the MVC pattern. ...

This is a continuation of my Introduction to ASP.NET MVC series. As I outlined before this is in an effort to write the book and keep blogging, I decided to write/blog the last chapter, Chapter 2. I am doing this so I can receive feedback on this chapter as early as possible. Because this chapter, in my opinion, is probably the most critical of the book, it defines the context around ASP.NET MVC and how it differs from ASP.NET Web Forms, as well as giving a historical perspective of the MVC pattern. ...

This is a continuation of my Introduction to ASP.NET MVC series. As I outlined before this is in an effort to write the book and keep blogging, I decided to write/blog the last chapter, Chapter 2. I am doing this so I can receive feedback on this chapter as early as possible. Because this chapter, in my opinion, is probably the most critical of the book, it defines the context around ASP.NET MVC and how it differs from ASP.NET Web Forms, as well as giving a historical perspective of the MVC pattern. ...