Archive

Archive for August, 2009

Setting up a PHP Development Server on Windows

August 19th, 2009 No comments

I know of four different ways to do this. I’m going to cover them in the order of my personal preference (and ease).

Install WAMP

Wamp is probably the easiest quickest way to get an apache server running PHP on your computer.

Just download the install here: Wamp Download run it, use the tool to make sure you don’t have anything running on port 80, and start the two services (apache, and mysql) by right clicking the icon in the task bar and clicking “Run All Services”

Download and Run Uniform

Uniform is different from WAMP and XAMP in that there is nothing to install, you just download it, and run it. This provides you with the ability to create a seperate “server” for each project you do, with it’s own mysql and apache binaries, configs, etc… I, personaly, perfer WAMP and writing all my apps to be location agnostic, so that they run anywhere and co-exist peacefully, but you may prefer this.

Install XAMPP

XAMPP is like WAMP. You download it, install it, and click go, but the only time I tried it (a few years ago) I ran into some difficulties. At the time they didn’t have a control panel like WAMP. This may in fact be the superior way to go, but I like my WAMP.

Setup Apache, MySQL, and PHP Binaries.

I did this once. It took me a few days (this was like 3 years ago, when my experience with PHP was ‘nill) If your a masochist this is the way to go. You’ll learn all the nitty gritties (or atleast be impeded by them). Hopefully you can beat my time.

Categories: 100 Weeks of PHP, php5 Tags:

ASP StateServer you MUST set the MachineKey!!!

August 18th, 2009 No comments

I just spent 2 hours beating my head against the wall trying to get the aspnet_state.exe stateserver to work right… Everything was configured, on my desktop the site worked flawlessly when running on Cassinni, and yet, whenever I moved it to production, the sessions were still disappearing when we restarted w3wp.exe… The problem? IIS6 was generating a new Machine Key for each worker process… (I assume this is the default behaivor, but I don’t know). Just setting that in stone in the web.config file fixed the problem. And now, I am dancing with glee because we can use worker process recycling, and end the w3wp.exe process at will without effecting anyone. YAY!!!!

Categories: Asp.Net Tags: