Archives
-
Quickies vs. Performance - Part 1
One thing I've noticed of the past few years is the amount of developers/programmers/ninjas that do take the easy and quick way to do certain tasks.
With each release of .NET things get easier for us. Things are bundled together, we have to do fewer checks, and it's all nice. But, as much as we're being spoiled by all these cool encapsulated functions, we're forgetting some very basic coding practices.
C# has garbage collection, so why should we have to destroy objects? There are timeouts on SQL Connections, so why should we close DataReaders? Servers these days are so powerful it's ok if I make every ASP.NET object global... it makes my code easier...
What's happened to us? Now some of you might think: "That can't be so Ryan. No one would do that." Unfortunately it's true. With many new developers hitting the main stage this is becoming more and more of an epidemic. -
Master Pages, buttons, Login Control, and the default button
<asp:Panel ID="pnlLogin" runat="server" DefaultButton="LoginButton">
-
The Woes of Windows XP... one website? or more?
Recently I was forced to reinstall XP on my lappy. First off the wireless card hated Vista, and well... I'm not a fan of having a laptop in a stationary place... I like to "roam".
So, rather than go through the plain ol' WinXp install, I decided to try LastXP. I already own XP, Office 2007, VS 2005 etc. so I have no qualms whatsoever in installing LastXP. (One thing nice about LastXP is that you can have the Vista Sidebar, task switching, etc. all with it).
So now I'm back on XP. I go and refresh my Development folders, and bring over the few websites I'm working with and then it hits me: "ONLY ONE WEBSITE ON XP!?!?!"... Yea, that bummed me out. However, I did find a beautiful script that allows me to bypass this "one website" crap that was forced onto me.
So, How do you get mulitple sites? Well it's quite easy actually, all you need to do is run one simple script.