使用 Server 2008 64 位上的本机集成管道模式将网站从 IIS 6.0 上运行转换为 IIS 7.0
总结
为了让我的网站在64位服务器平台上顺利运行,使用IIS 7.0集成管道模式,我需要修复哪些问题为了使其发挥作用。
更多细节
我知道,如果程序集使用 PInvoke 并且我在项目中引用了此类程序集,那么我收到的错误消息可能会非常模糊和晦涩。
- 我该如何找到这些程序集?
- 如果我查看带有反射器的 dll,并且没有 PInvoke,是否足以假设该 dll 在 64 位环境中正常?
关于如何检查我的网站是否完全兼容 64 位有什么具体建议吗? 将其编译为 AnyCPU 是否足以确保其在集成管道模式下正确运行?
谢谢 日韩
Summary
To get my site running smoothly on a 64bit server platform, using IIS 7.0 Integrated pipeline mode, what are the things I would need to fix in order for this to work.
Some more detail
I am aware of, that if a assembly uses PInvoke and I have a reference to such a assembly in my project, the error message I will get will probably be very vague and obscure.
- How do I go about finding these assemblies?
- If I look at a dll, with reflector, and there is no PInvokes, would this be sufficient to assume that the dll, would be fine in a 64 bit environment?
Any specific suggestions on how to check that my site is fully 64 bit compatible? Would compiling it as AnyCPU be sufficient to ensure that it will run correctly in Integrated pipeline mode?
Thanks
Rihan
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
我们已经找到了有问题的dll,购买一个程序来消除。 遗憾的是我无法提供更“科学”的方法。
我通过这个过程学到了什么:
您可能不必处理这些问题,但在您之后的开发人员将不太尊重您。
We have found the offending dll, buy a process of elimination. So sadly I cant offer a more "scientific" approach.
What I have learned through this process:
You probably wont have to deal with this issues, but developers that come after you will have less respect for you.