Getting Set For Production Deployment

posted on 2005-03-28 at 23:44:39 by Joel Ross

As we near the final days of testing, we're also getting ready for deployment to production. That means all those configuration settings need to be looked at, and adjusted to be production ready.

One that I always see is to change the compilation tag in the web.config to have debug="false". It makes sense - you don't want debug code in production. Combine that with a release build, and you'll get the better performance.

So we did that. I tested it locally, and immediated had issues. It said a user control was defined in multiple places. I couldn't figure anything out, but the same control name was used in multiple places, just in different namespaces. I solved the issue by renaming one of the controls, and the web server was happy again. But I don't know why that worked. We have other user controls with the same name, but that one caused problems. Very strange. Any one have any ideas?

Regardless, we are in the final hours before we go to production. I'm excited. The client asked me if I was nervous. I have a pretty big project that I was the technical lead on that is about to launch, there's the Final Four, which Tourney Logic has a big stake in, and then I have a baby being born. All finishing up within a week. And my wife is on bedrest. You'd think I would be stressed. Oddly, I'm not. I'm just ready to get them all out the door, so to speak!

Categories: ASP.NET