On compatibility side, not all the web applications and dependencies are 64 bit ready. Start from 32 bit on IIS help avoid lots of trouble at the very beginning. If your application happens to be 64 bit ready, you can start from 64 bit. Otherwise, you are stuck.
Microsoft does not have good tools to debug 64 bit issues for non-advanced developers yet (in 2008 that was true, and it is true even today). Even if you are an IIS geek, debugging 32 bit worker process is much simpler than debugging the 64 bit one.
The migration to 64 bit will finally finish (thinking about the 16 to 32 bit migration in 1990s).
I don't believe that you should stick to "Microsoft recommends 32 bit" or "Steve Scholfield said that". All should depend on your own application, and your unique environment. Those conclusions were drawn for other scenarios, which may not even apply a bit to your case.
Edited: In fact Microsoft's guys explain the performance gain of using 32 bit better in this VS related blog post,
发布评论
评论（1）
在兼容性方面，并非所有 Web 应用程序和依赖项都支持 64 位。在 IIS 上从 32 位开始有助于避免一开始的很多麻烦。如果您的应用程序恰好支持 64 位，则可以从 64 位开始。否则，您就会陷入困境。
Microsoft 还没有好的工具来为非高级开发人员调试 64 位问题（在 2008 年确实如此，即使在今天也是如此）。即使您是一名 IIS 极客，调试 32 位工作进程也比调试 64 位工作进程简单得多。
向 64 位的迁移将最终完成（想想 20 世纪 90 年代从 16 位到 32 位的迁移）。
我不认为您应该坚持“微软推荐 32 位”或“史蒂夫·斯科菲尔德说过”。一切都应该取决于您自己的应用程序和您独特的环境。这些结论是针对其他情况得出的，甚至可能不适用于您的情况。
已编辑： 事实上，Microsoft 的人员在这篇 VS 相关博客文章中解释了使用 32 位更好的性能增益，
http://blogs.msdn.com/b/ricom/archive/2009/06/10/visual-studio-why-is-there-no-64-bit-version.aspx
On compatibility side, not all the web applications and dependencies are 64 bit ready. Start from 32 bit on IIS help avoid lots of trouble at the very beginning. If your application happens to be 64 bit ready, you can start from 64 bit. Otherwise, you are stuck.
Microsoft does not have good tools to debug 64 bit issues for non-advanced developers yet (in 2008 that was true, and it is true even today). Even if you are an IIS geek, debugging 32 bit worker process is much simpler than debugging the 64 bit one.
The migration to 64 bit will finally finish (thinking about the 16 to 32 bit migration in 1990s).
I don't believe that you should stick to "Microsoft recommends 32 bit" or "Steve Scholfield said that". All should depend on your own application, and your unique environment. Those conclusions were drawn for other scenarios, which may not even apply a bit to your case.
Edited: In fact Microsoft's guys explain the performance gain of using 32 bit better in this VS related blog post,
http://blogs.msdn.com/b/ricom/archive/2009/06/10/visual-studio-why-is-there-no-64-bit-version.aspx