Categorized Under: ASP.NET

This is a short post and I'm writing this because I've seen a lot of people using or and not using the overloads:

So rather than repeat the same thing over and over, I've decided to write a blog post about it in the hopes that others may find it and learn from it[...]

During the design and development of Quartz for ASP.NET and Orion, performance was an extremely important area I focused on. Optimizing a framework such as Quartz for ASP.NET is important because other websites and application will be built using it and I believe it is imperative that frameworks pay close attention to performance[...]

Orion is a high performance blogging engine written using the Quartz for ASP.NET framework. This blog is now powered by the Orion engine, so what you see by way of features, function and speed (responsiveness) is what you get with the Orion engine and of course the Quartz for ASP.NET framework. I was initially using WordPress for my blog (this blog) and eventually just got tired of having to deal with some of the nuances of WordPress and more specifically the theme I was using[...]

When I started down the path of writing the Orion engine (a high performance blogging engine written in Quartz for ASP.NET), which is what drives this website, I wanted to be able to use Windows Live Writer to write my blog posts and so that need sent be down this path and so here we are[...]

The typical model of instantiating your Business Layer or business classes is to create an new instance each time you are servicing a request. That is, in your page or controller, you create a new instance of your business layer. Is there another way to do this and what would be the advantages? And would it be thread-safe? Yes, there is and the option I'll be presenting in this post has a few advantages as well. However, before we going into the details of this option we need to understand how things work insofar as IIS and the ASP[...]

The genesis of Quartz for ASP.NET was what I felt were some Problems with ASP.NET MVC Framework Design. Quartz for ASP.NET can be used in conjunction with ASP.NET MVC or in regular ASP.NET WebApplication/Website projects (without any WebForms). It works the same either way.   [...]

The MVC design pattern is probably the most misunderstood and misinterpreted design pattern. It’s probably due to this that the various implementations of the MVC design pattern are so different. Another way to look at it is that the MVC design pattern is not the most suitable design pattern for web based applications and as a result, many implementations/interpretations of the MVC design pattern go against the original intent. This article is about what I think are the problems with the design and implementation of Microsoft’s ASP[...]

As part of ASP.NET MVC3, we get a brand spanking new View Engine. In MVC2 the view engine we have access to by default is the ASP.NET Webforms view engine that uses Master file templates along with .aspx view templates and .ascx partial view templates. In ASP.NET MVC, the view engine is responsible for parsing and compiling your views and partial views into C# or other .NET languages so as to be able to render the view into an html page. As it stands today in ASP[...]