使用 AjaxControlToolkit 迁移到 Web 应用程序
目前,我们正在将 ASP.NET 网站迁移到 Visual Studio 2008 中的 Web 应用程序。大部分过程都相当简单,但我遇到了一个让我有点抓狂的障碍。
我们使用 AjaxControlToolkit 来实现某些功能,特别是 AutoControlExtender。当通过 VS 的开发服务器在本地运行时,扩展器(下拉列表)在服务返回结果集后不会呈现。但是,如果我将迁移的解决方案部署到我们的 UAT 服务器,则扩展器可以正常运行。
我已确保 Ajax 控制工具包在我的开发计算机上本地正确安装(并且 dll 在 bin 目录中可用),并且使用调试确保服务被正确调用并且运行无错误(确实如此)。 Web 应用程序取自运行 IIS7 的服务器。
任何人都可以确认 Visual Studio 2008 开发服务器是否需要与 IIS 7 不同的配置(因为我相信 IIS 6 需要与 IIS 7 不同的配置),以及是否有资源提供更多信息?我自己的搜索在这方面的成果很少。
另一方面,如果我在错误的区域寻找任何其他提示,我们将不胜感激。
谢谢 克里斯
We are currently migrating our ASP.NET website to a web application in Visual Studio 2008. Most of the process has been fairly straight forward, but I have hit one block that is driving me a bit nuts.
We are using the AjaxControlToolkit for some functionality, specifically an AutoControlExtender. When this is run locally through VS's development server the extender (dropdown) does not render after the service returns the resultset. However if I deploy the migrated solution to our UAT server the extender functions correctly.
I have ensured the Ajax Control Toolkit is properly installed locally on my dev machine (and the dll available in the bin directory), and using debugging have ensured the service is called correctly and runs through without error (which it does). The web application was taken from a server running IIS7.
Can anyone confirm if Visual Studio 2008 development server requires a different configuration to IIS 7 (as I believe IIS 6 requires a different configuration to IIS 7), and if there is a resource that provides more info? My own searches have turned up very little in this area.
On the other hand, if I am looking in the wrong area any other tips would be appreciated.
Thanks
Chris
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
嗯,终于找到问题了,如果以后有人遇到这个问题,欢迎评论。
在我们的解决方案中,页面所在的特定文件夹有一个辅助 web.config 文件。里面没有太多东西,它似乎是由于历史原因而存在的。
删除辅助文件似乎允许 VS 的 Web 服务器从根 web.config 加载正确的配置,并且下拉菜单有效。
Well, finally found the problem, and commenting if anyone gets this in the future.
In our solution the specific folder the page was in had a secondary web.config file. There was not much in there, it seemed to exist for historical reasons.
Removing the secondary file seemed to allow VS's web server to load the correct configuration from the root web.config, and the drop down worked.