I'm a big fan of strongly typed database querying as well as returning strong typed results. Due to the nature of static languages, you'll get compile time checking of all our tables and columns. You can easily rename columns as you can be sure all your (internal) references are accounted for.
Read the complete 18446 bytes...
Digg it |
Kick it |
Dzone it |
Reddit
Time flies fast. Back in 2006, during my time as an
MSP, I made a series of presentations on securing intellectual property in .NET code, resulting in my
Securing .NET Code article. Although it's about two years old, most points are still valid today, unfortunately.
Read the complete 1209 bytes...
Digg it |
Kick it |
Dzone it |
Reddit
I often do code profiling, usually involving a stopwatch and some boilerplate code. I decided to make a quick'n'simple class that'll help me get rid of some of that code and concentrate on the actual code being profiled.
Read the complete 4397 bytes...
Digg it |
Kick it |
Dzone it |
Reddit
In my
earlier blog post about the dangers of using Response.TransmitFile, I gave an example of a workaround involving spawning a new thread in the ASP.NET page. While this does solve the issue at hand, it presents us with a new way to kill our application even quicker than last.
Read the complete 3463 bytes...
Digg it |
Kick it |
Dzone it |
Reddit
Before attempting to optimize code or fix any kind of load issue, you should first gather data and become aware of what bottlenecks you're experiencing. A great way to do this is through the Performance Monitor application. Recently I tried monitoring my ASP.NET applications, but all my counters had a value of 0. As I thought initially, it's a simple problem, but the solution was not easily found.
Read the complete 1637 bytes...
Digg it |
Kick it |
Dzone it |
Reddit