tag:blogger.com,1999:blog-50637648113408287432024-09-01T19:20:50.028-03:00Thiago Sayao's blogThiago M. Sayãohttp://www.blogger.com/profile/02570373698216968720noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-5063764811340828743.post-25834751455177180862010-09-09T22:53:00.004-03:002010-09-13T22:14:01.096-03:00

dotnetburner.com was a community site much like http://dotnetshoutout.com or http://dotnetkicks.com, but it did not work for some reasons (my lack of time and “marketing” skills for example) so i closed it. But since it has a nice code base based on asp.net mvc i decided to release the source (was originally coded for mvc 1 but i ported it to mvc 2 with just a few changes). It serves as example

Thiago M. Sayãohttp://www.blogger.com/profile/02570373698216968720noreply@blogger.com0tag:blogger.com,1999:blog-5063764811340828743.post-65438116695666236832009-08-18T21:40:00.002-03:002010-07-21T21:03:15.642-03:00

With this implementation you can re-use parts of your content Controller (the database query for example) and render it on a RSS and/or ATOM feed. Let's say you have an action like this (extracted from DotNetBurner’s source): [AcceptVerbs (HttpVerbs.Get | HttpVerbs.Head), CompressFilter] public ActionResult Upcoming (int? page, string sort) { var

Thiago M. Sayãohttp://www.blogger.com/profile/02570373698216968720noreply@blogger.com2tag:blogger.com,1999:blog-5063764811340828743.post-27716302299515971742009-08-11T21:27:00.005-03:002010-09-13T22:13:23.629-03:00

This article explains an approach to lazy load a database query on an ASP.net MVC controller to prevent the query from executing on it, and just execute on the View, if it's not cached. So, if the View is cached, the database is not queried. With ASP.net MVC you would obviously have a Model, a View and a Controller. But the workflow of a page execution on MVC is not really M-V-C, because it

Thiago M. Sayãohttp://www.blogger.com/profile/02570373698216968720noreply@blogger.com0tag:blogger.com,1999:blog-5063764811340828743.post-52252990077716721512009-08-01T10:11:00.002-03:002010-07-21T21:04:31.320-03:00

This post shows a real scenario on using included columns on SQL Server 2005/2008 to improve the response time of an ASP.net resource. When developing DotNetBurner, i wanted to make sure that the site performance was the best it could be. Targeting this goal, i have used indexes with included columns to improve the response time of the "burn!" count image. The burn count image shows how many "

Thiago M. Sayãohttp://www.blogger.com/profile/02570373698216968720noreply@blogger.com0tag:blogger.com,1999:blog-5063764811340828743.post-39207574746007904852009-07-30T21:19:00.002-03:002010-07-21T21:04:48.157-03:00

The PIVOT operator is used to transform rows into column by an aggregate function. One big limitation is that you have to know the columns, but still, it's useful on some use cases, like when you want to aggregate something by hours (for example). About having to know the column names limitation: This is probably a design decision, because someone could write a query that has too many columns

Thiago M. Sayãohttp://www.blogger.com/profile/02570373698216968720noreply@blogger.com0tag:blogger.com,1999:blog-5063764811340828743.post-4599437999305191182009-07-30T21:04:00.002-03:002010-07-21T21:05:14.690-03:00

It is common to have to execute a mass update on some table, for example, to update a customer credit classification. When such updates are executed, you may want to know what has changed and maybe log it. There are several ways to do it, but i recently found one that makes it easier: the OUTPUT clause. First, we create a customer table for the example and populate it with some data:IF

Thiago M. Sayãohttp://www.blogger.com/profile/02570373698216968720noreply@blogger.com0tag:blogger.com,1999:blog-5063764811340828743.post-60395696822701985702009-07-27T20:45:00.004-03:002010-07-21T21:05:31.961-03:00

It is common to have some code that is part of some workflow and you don’t want it to execute when you are testing. For example, if your code sends an e-mail to some users, you don’t want to crud your users mail box with e-mails originated from your tests. Unless you are testing if sending the e-mail works, you can do this to test the rest of your code: static void SendMail(string to,

Thiago M. Sayãohttp://www.blogger.com/profile/02570373698216968720noreply@blogger.com0tag:blogger.com,1999:blog-5063764811340828743.post-82028627120828925362009-07-22T20:11:00.005-03:002010-07-21T21:05:50.265-03:00

When thinking about performance, one of the top things that comes in mind is caching. Caching means that you will save some server resources by saving the result on the “first” time it’s processed. With ASP.net MVC, it’s common the use of HTML Helpers, that are just methods that return a resulting HTML. We can combine both and cache the resulting HTML on the first time the method is called,

Thiago M. Sayãohttp://www.blogger.com/profile/02570373698216968720noreply@blogger.com0