I posted some input on your blog, very nice directions by the way :)
I am currently still doing some testing and writing up a few things
before I package the final 1.1.0 release, but it's pretty close to
done as far as the DLL code goes. If you want to try compiling it,
just check it out from svn again and hopefully it'll work fine. I'm
probably going to stop packaging a source release and force people to
check out from subversion since the SubWCRev tool is required anyway.
The most important change for people compiling code is that you can
install a non-default Python (deselect "register extensions" during
setup) in the $(SolutionDir)\Python\arch folders (i386 for 32-bit, x64
for 64-bit) and the project should auto-magically find the libraries,
includes, and even the Python core DLLs for that specific version if
you debug on the same machine (works for 2.6 at least, not sure about
2.5). I know this won't be as simple for you because you're compiling
for 64-bit on a 32-bit system, but you can manually drop the folders
in the right places too.
My goal there was to make sure that it's somewhat easier to compile
the code right out of the box. This will work with the "Release"
configurations for x86 and x64, I can't guarantee that the Debug
configuration is anything useful at the moment however.
Now, to your issue with IIS7, which ironically may not be related to
compiling from source: did you check permissions (NETWORK SERVICE) and
the "allowed extensions" configuration? IIRC, not allowing the
PyISAPIe DLL to be executed will result in 404s. As far as the
permissions go, make sure your Python64 installation folder has the
same permissions as the 32-bit folder. Also, did you use the installer
for the 64-bit version on the server?
I know this is just basic troubleshooting stuff, but it's good to get
that out of the way before considering bigger problems :)
- Phillip