The only limitation is that you can only run one website at a time. You can
configure multiple sites, but only one can be in the "start" state at a time
- there are tools available to make switching between active sites simple
however so it's a minor problem for development.
On XP Home you may be able to get IIS running, but only via hacking (the one
technique I've seen requires you to copy several files from a working XP Pro
installation), but it would be easier to just use a different web server
(either the CFMX built-in server or Apache would work fine).
Lastly, if your machine is powerful enough the coolest and most versatile
solution is running a virtual machine (I use MS Virtual PC, formerly by
Connectix but VMWare is also good). Then you can install Win2K into a VM
and dedicate it as a server. You then develop against this server
(effectively mimicking a much more realistic production-like environment).
You can have as many VPCs available as you have Disk space to store them and
can run as many at once as your RAM will support. You could have one
dedicated to each product that has its own production server, have dedicated
VPCs for different versions of CF or Web Servers and so forth. Once you get
into the habit you'll never want to go back.
Jim Davis
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
