As developers code their applications, they should immediately think about security in their design right from the get-go.
However, if it's a legacy system and they don't have the luxury of implementing security into the design, you need to play "little Dutch boy" and plug the existing holes of your application (I know, I know...you probably don't have any holes in your code, but humor me...)
Even though I thought I had this nailed down last week, I decided to toss in the towel regarding the Multiple Project Area Support issue.
I ran across various posts, but the clincher was this forum post on the ASP.NET Forums about Area support in ASP.NET MVC 2 RC.
I guess I need to take a different approach.
Let's flash back to when I started developing with ASP.NET MVC pre-2.
When I started building my CMS (Content Management System) using ASP.NET MVC 2 Preview 2, Areas were a major factor in my development. I was elated that the ASP.NET MVC Team integrated them into the release, but I ran into a problem...where do I start?
Since ASP.NET MVC came out last year, I've been writing every project in ASP.NET MVC.
Now, that ASP.NET MVC 2 RC is released, my primary focus for this release is on the modular aspect using areas. If you are a web developer with .NET and have not experienced ASP.NET MVC yet, this is definitely the time to move into a new technology and direction as a web developer.
Quick .NET 4.0 Links
I've been working on a project and got the dreaded error:
"A potentially dangerous Request.Form value was detected from the client"
Well, after trying the "<@page validateRequest="false"...>", I realized that didn't work. So I started looking through the code and found the attribute:
You need to attach the ValidateRequest(false) attribute to the method that is receiving the post.
I'm starting up a little "group" in Twitter for developers called the Programmer Thought of the Day (#PTOTD).
I already posted one, but if anyone wants to add additional thoughts under the Twitter #PTOTD hashtag, please do.
My Twitter handle is jdanylko
Lately, I've been diving heavily into ASP.NET MVC and jQuery. I really like them! No, I mean I really like them!
Some of the side-projects I've been building over the past year came together when I was introduced to ASP.NET MVC, and since then, I haven't turned back yet ("Web Forms? Feh").
If you are new to ASP.NET MVC, I would recommend Phil Haacked's site. Not one article, but his entire site. Since he was one of the co-authors of ASP.NET MVC framework, it only stands to reason to blog about it. I would recommend one of his articles though: Everything you wanted to know about MVC and MVP but were afraid to ask.
Collected for your convenience...all in one location over the past two months.
First, the primary link for the ASP.NET MVC Beta.
Then, the additional articles and tutorials: