同一台服务器上部署ASP.net AJAX 1.0和3.5的Web应用程序 [英] Deploying ASP.net Ajax 1.0 and 3.5 web application on same server
问题描述
我们与阿贾克斯1.0运行和相应的工具（工具包版本1.0.20229）生产服务器里面有ASP.net 2.0应用。
我被要求使用移动3.5 ASP.net另一个应用程序的构建也utalizes最新的ASP.NET AJAX和相应的工具（工具包3.0.x版）。
可以将这两个应用程序在同一服务器上存在，如果我安装.NET Framework 3.5（当前版本的服务器上为2.0）？
什么都应该怎么做，以确保不存在兼容性问题？
请让我知道，如果这个问题不明确。
感谢您，
在三月
结果：
安装框架3.5。
根据错误更改配置文件作了收到了这些包括：
删除folloeing条目：
＆LT;＆的HttpModules GT; ＆LT;添加名称=ScriptModuleTYPE =System.Web.Handlers.ScriptModule，System.Web.Extensions程序，版本= 3.5.0.0，文化=中性公钥= 31BF3856AD364E35/＆GT; ＆LT; /＆的HttpModules GT;
不得不采取出WCF服务的以下部分，除了上述
＆LT; sectionGroup NAME =System.Web.Extensions程序TYPE =System.Web.Configuration.SystemWebExtensionsSectionGroup，System.Web.Extensions程序，版本= 3.5.0.0，文化=中性公钥= 31BF3856AD364E35＆GT;
该应用程序应该罚款运行并排侧。
如果您正在分发了AJAX控件工具包作为一个本地引用.dll文件（换句话说，你已经加入该.dll文件到您的项目，并引用了本地文件），那么你应该有该工具包没有问题
对于阿贾克斯（System.Web.Extensions程序）引用，你可以做两件事情：
2）通过在项目中引用你去设置SpecificVersion等于真，这将迫使工程总引用2.0版吧
3）只需使用3.5版本。如果SpecificVersion未设置为true，这可能会自动发生，但如果没有，你可以使用web.config中的的 bindingRedirect 的元素，像这样：
＆LT;结构＆gt;
＆LT;＆运行GT;
＆LT; assemblyBinding＆GT;
＆LT; dependentAssembly＆GT;
＆LT; assemblyIdentity名称=System.Web.Extensions程序
公钥=31bf3856ad364e35
文化=中性/＆GT;
＆LT; bindingRedirect oldVersion =1.0.61025.0
NEWVERSION =3.5.0.0/＆GT;
＆LT; / dependentAssembly＆GT;
＆LT; / assemblyBinding＆GT;
＆LT; /运行＆GT;
＆LT; /结构＆gt;
这方法是最侵入性的，因为你不必在所有接触到的项目。这也将适用于任何第三方DLL的有System.Web.Extensions程序的1.0版本明确的引用。
我从使用Ajax的2.0框架的版本3.5版本升级的项目，并没有一个单一的问题。
祝你好运！
We have a production Server which has ASP.net 2.0 Application running with Ajax 1.0 and corresponding toolkit (Toolkit version 1.0.20229).
I have been asked to move another application build using ASP.net 3.5 which also utalizes latest ASP.NET AJAX and corresponding toolkit (Toolkit Version 3.0.X).
Can these two application exist on the same server, if I install .Net Framework 3.5 ( current version on the server is 2.0)?
What all should I do to make sure there is no compatability issues?
Please let me know if the question is not clear.
Thank you,
The Mar
RESULT: Installed Framework 3.5. Changes to config file were made according to errors received these include: removed the folloeing entry:
<httpModules> <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/> </httpModules>
Had to take out the following section for WCF service in addition to above
<sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
The applications should be fine running side-by-side.
If you are distributing the ajax control toolkit as a locally referenced .dll (in other words, you've added the .dll file to your project, and referenced that local file), then you should have no problems with the toolkit.
As for the Ajax (System.Web.Extensions) references, you can do two things:
2) Go through the references in the project and set "SpecificVersion" equal to "true", and that'll force the project to always reference the 2.0 version of it
3) Just use the 3.5 version. If SpecificVersion isn't set to true, this might happen automatically, but if not, you can map the reference in your first project by using the web.config's bindingRedirect element like so:
<configuration>
<runtime>
<assemblyBinding>
<dependentAssembly>
<assemblyIdentity name="System.Web.Extensions"
publicKeyToken="31bf3856ad364e35"
culture="neutral" />
<bindingRedirect oldVersion="1.0.61025.0"
newVersion="3.5.0.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>
This method is the least invasive, as you don't have to touch the project at all. This will also work for any third party dll's that have explicit references to version 1.0 of System.Web.Extensions.
I've upgraded projects from using the 2.0 framework's version of Ajax to the 3.5 version, and haven't had a single problem.
Good luck!
这篇关于同一台服务器上部署ASP.net AJAX 1.0和3.5的Web应用程序的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
