{"id":4934,"date":"2007-07-28T15:50:00","date_gmt":"2007-07-28T15:50:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/webdev\/2007\/07\/28\/upgrading-asp-net-ajax-1-0-websites-and-web-applications-to-net-framework-3-5\/"},"modified":"2007-07-28T15:50:00","modified_gmt":"2007-07-28T15:50:00","slug":"upgrading-asp-net-ajax-1-0-websites-and-web-applications-to-net-framework-3-5","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/upgrading-asp-net-ajax-1-0-websites-and-web-applications-to-net-framework-3-5\/","title":{"rendered":"Upgrading ASP.NET AJAX 1.0 Websites and Web Applications to .NET Framework 3.5"},"content":{"rendered":"

\n

\n

8\/10\/2007 UPDATE:  <\/SPAN><\/B>This blog post was edited to include simplified instructions to work around a known issue w\/ Multitargeting support in VS 2008 Beta 2.  <\/SPAN>See \u201cMachine Prerequisites\u201d below.<\/FONT><\/P><\/DIV>\n

<\/FONT><\/FONT> <\/P>\n

Microsoft Visual Studio 2008 Beta 2 is finally released, and with it comes a bunch of great new features for writing and maintaining ASP.NET AJAX applications.  <\/SPAN>Additionally, a new version of ASP.NET AJAX is included in the .NET Framework 3.5, which includes improvements over the current ASP.NET AJAX 1.0 release.  <\/SPAN>This article walks you through the steps you\u2019ll need to follow to upgrade your existing ASP.NET AJAX 1.0 Websites and Web Application Projects to use the AJAX support in .NET Framework 3.5 and Visual Studio 2008 Beta 2.<\/FONT><\/P>\n

<\/FONT> <\/P>\n

Note: <\/I><\/B> <\/SPAN>With the new Multitargeting support in Microsoft Visual Studio 2008, It is also possible to continue maintaining ASP.NET AJAX 1.0-based Websites and Web Application Projects in VS 2008 without upgrading them.  <\/SPAN>Click here<\/A> to learn the steps you can take to maintain and\/or create new ASP.NET AJAX 1.0 applications using Microsoft Visual Studio 2008 Beta 2.<\/I><\/FONT><\/FONT><\/P>\n

<\/I><\/FONT><\/FONT> <\/P>\n

Machine Prerequisites:<\/SPAN><\/B><\/P>\n

 <\/P>\n

1.       <\/SPAN><\/SPAN><\/SPAN>Download and install Microsoft Visual Studio 2008 Beta 2<\/A><\/P>\n

2.       <\/SPAN><\/SPAN><\/SPAN>After the Beta 2 installation has finished, you should run this script<\/A> to ensure that the installation of .NET Framework 3.5 Beta 2 will not affect the development of ASP.NET AJAX 1.0 applications.  <\/SPAN>You should do this immediately<\/EM> after installing VS Beta 2. <\/P>\n

3.       <\/SPAN><\/SPAN><\/SPAN>Apply the following workaround to fix a known issue with Visual Studio\u2019s Multitargeting support for AJAX 1.0.  <\/SPAN>Note that this workaround will *not* be required for the VS 2008 RTM release:<\/P>\n

 <\/P>\n

\n

Workaround to Fix VS 2008 Beta 2 Multitargeting Support for AJAX 1.0<\/B><\/P>\n

 <\/P>\n

    <\/SPAN>1.  <\/SPAN>In Window\u2019s Explorer, go to this folder:
         \\Program Files\\Reference Assemblies\\Microsoft\\Framework\\v3.5<\/EM><\/P>\n

    <\/SPAN>2.  <\/SPAN>Create a folder entitled \u201cBackup\u201d at this location<\/P>\n

    <\/SPAN>3.  <\/SPAN>Make a back-up copy of these two assemblies in the new \u201cBackup\u201d folder, and 
         then<\/B> delete<\/B> them<\/B> from \\Program Files\\Reference Assemblies\\Microsoft\\Framework\\v3.5<\/EM>:<\/P>\n

 <\/P>\n

               <\/SPAN>System.Web.Extensions.dll<\/I><\/P>\n

               <\/SPAN>System.Web.Extensions.Design.dll<\/I><\/P>\n

   <\/SPAN><\/P>\n

Note:<\/B>  <\/SPAN>This workaround causes two known side effects to Web Application Projects in VS 2008:
 <\/SPAN><\/U><\/P>\n

Creating a new 3.5 Web Application Project has a “broken” reference to System.Web.Extensions 0.0.0.0 in the client references list (Project Properties > References).<\/I><\/B>  <\/SPAN>If you build the project, you will encounter this error:  <\/SPAN><\/I><\/B>The referenced assembly “D:\\Program Files\\Reference Assemblies\\Microsoft\\Framework\\v3.5\\System.Web.Extensions.dll” was not found. If this assembly is produced by another one of your projects, please make sure to build that project before building this one. <\/SPAN>In order to correct this, you need to manually remove this reference, then Browse… to the location of the System.Web.Extensions 3.5 backup you made in step 3 above to add the reference back to the project.<\/I><\/B><\/P>\n

 <\/P>\n

When upgrading a Web Application Project that uses AJAX 1.0 to .NET Framework 3.5, VS doesn’t remove the reference to System.Web.Extensions 1.0.6<\/I><\/B> in the client references list (Project Properties > References).  <\/SPAN>You need to manually remove this reference and then Browse… to the location of the System.Web.Extensions 3.5 backup you made in step 3 above to add the reference back to the project.  <\/SPAN>This issue and workaround is described in more detail below.<\/P><\/DIV>\n

 <\/P>\n

Step One:  <\/SPAN>Upgrade Your ASP.NET AJAX Website<\/SPAN><\/B><\/P>\n

 <\/P>\n

1.       <\/SPAN><\/SPAN><\/SPAN>First, make a backup of your project, then launch Microsoft Visual Studio 2008 Beta 2.<\/P>\n

2.       <\/SPAN><\/SPAN><\/SPAN>In the File menu, choose Open Website\u2026 to open your Website\u2019s folder or IIS virtual directory<\/P>\n

a.       <\/SPAN><\/SPAN><\/SPAN>If you are opening a Web Application project instead, choose \u201cOpen Project\u2026\u201d, and navigate to the project file to open it.  <\/SPAN>Follow the steps of the Visual Studio Conversion wizard to migrate the project.<\/P>\n

3.       <\/SPAN><\/SPAN><\/SPAN>When Visual Studio 2008 prompts to upgrade the Website or Web Application, select \u201cYes\u201d<\/P>\n

<\/EM> <\/P>\n

\"Framework<\/P>\n

 <\/FONT><\/FONT><\/P>\n

\n

Important Note:  <\/SPAN><\/B>When upgrading a Web Application Project that uses AJAX 1.0 to .NET Framework 3.5, VS doesn’t remove the reference to System.Web.Extensions 1.0.6 in the client references list (Project Properties > References).  <\/SPAN>You need to manually remove this reference and then Browse… to the location of the System.Web.Extensions 3.5 backup you made in step 3 above to add the reference back to the project, following these steps:<\/B><\/FONT><\/FONT><\/P>\n

 <\/FONT><\/P>\n

1.  <\/SPAN>Right-click the project node in Solution Explorer, and choose \u201cProperties\u201d<\/FONT><\/P>\n

2.  <\/SPAN>Click the \u201cReferences\u201d tab<\/FONT><\/P>\n

3.  <\/SPAN>Click the reference to \u201cSystem.Web.Extensions\u201d version 1.0.6 and click the \u201cRemove\u201d button<\/FONT><\/P>\n

4.  <\/SPAN>Click the \u201cAdd Reference\u201d button<\/FONT><\/P>\n

5.  <\/SPAN>Switch to the \u201cBrowse\u201d tab<\/FONT><\/P>\n

6.  <\/SPAN>Browse to the backup location for the 3.5 version of System.Web.Extensions.dll under \\Program Files\\Reference Assemblies\\Microsoft\\Framework\\v3.5\\Backup and click \u201cOK\u201d to add this reference.<\/FONT><\/P><\/DIV>\n

 <\/FONT>
Step Two:  <\/SPAN>Update the ASP.NET AJAX Control Toolkit assembly<\/FONT><\/SPAN><\/B><\/P>\n


If your application uses the <\/FONT>ASP.NET AJAX Control Toolkit<\/FONT><\/A>, you will need to follow these additional instructions to update the toolkit assembly in your application to a <\/FONT>new release<\/FONT><\/A> that works with .NET Framework 3.5:<\/FONT><\/P>\n

 <\/FONT><\/P>\n

1.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>Click here to go to the <\/FONT>ASP.NET AJAX Toolkit Release page<\/FONT><\/A><\/P>\n

2.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>Download the latest version of the toolkit for .NET Framework version 3.5 (choose one):<\/FONT><\/P>\n

a.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>AjaxControlToolkit-Framework3.5-NoSource.zip<\/FONT><\/P>\n

b.<\/FONT>      <\/SPAN><\/SPAN><\/SPAN>AjaxControlToolkit-Framework3.5.zip (includes source code)<\/FONT><\/P>\n

3.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>In Windows Explorer, right-click the zip file and choose \u201cExtract All\u2026\u201d to extract the contents to an \u201cAjaxControlToolkit-Framework3.5\u201d folder in the same directory<\/FONT><\/P>\n

4.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>Copy the AjaxControlToolkit.dll assembly from AjaxControlToolkit-Framework3.5\\SampleWebSite\\Bin to your application\u2019s Bin directory, replacing the previous version of the toolkit assembly<\/FONT><\/P>\n

 <\/FONT><\/P>\n

(Optional):  <\/SPAN>Install the ASP.NET AJAX Toolkit controls to the VS 2008 toolbox<\/U> <\/FONT><\/FONT><\/P>\n

You can also populate the toolbox in VS 2008 with the ASP.NET AJAX Toolkit controls by following these instructions:<\/FONT><\/P>\n

 <\/FONT><\/P>\n

1.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>Open a Web Form (.aspx page) in your project<\/FONT><\/P>\n

2.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>Right-click the Toolbox and choose \u201cAdd Tab\u201d<\/FONT><\/P>\n

3.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>Give the new tab a name, such as \u201cASP.NET AJAX Toolkit 3.5\u201d<\/FONT><\/P>\n

4.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>Right click underneath the new tab and select \u201cChoose Items\u2026\u201d (note that it can take awhile to bring up the this dialog for the first time) <\/FONT><\/P>\n

 <\/P>\n

\"Toolbox<\/P>\n

 <\/P>\n

5.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>In the Choose Toolbox Items dialog, click the Browse\u2026 button<\/FONT><\/P>\n

6.<\/FONT>       <\/SPAN><\/SPAN><\/SPAN>Browse to \\AjaxControlToolkit-Framework3.5\\SampleWebSite\\Bin, select AjaxControlToolkit.dll, and click the \u201cOpen\u201d button.<\/FONT><\/P>\n

 <\/P>\n

\"Toolbox<\/P>\n

 <\/P>\n

7.       <\/SPAN><\/SPAN><\/SPAN>You should see the toolkit controls selected in the Choose Toolbox Items dialog.  <\/SPAN>Click OK to add these controls to the toolbox.<\/P>\n

 <\/P>\n

\"Toolbox<\/P>\n

 <\/P>\n

Step Three:  <\/SPAN>Update Web.config to allow 3rd<\/SUP>-party AJAX 1.0 components to use .NET Framework 3.5<\/SPAN><\/B><\/P>\n

 <\/P>\n

As described above in Step Two, a new version of the Microsoft ASP.NET AJAX Control Toolkit is available that is compiled against the ASP.NET AJAX (System.Web.Extensions) assembly in .NET Framework 3.5.  <\/SPAN>However, your application may also be using 3rd<\/SUP>-party components\/assemblies that were compiled against ASP.NET AJAX 1.0.  <\/SPAN>In order for these components to continue working under the .NET Framework 3.5, you must add the following bindingRedirect section to the Web.config file of your ASP.NET AJAX 3.5 application.  <\/SPAN>This causes the 3rd<\/SUP>-party component to bind to the 3.5 version of System.Web.Extensions instead of the 1.0 version.<\/P>\n

 <\/P>\n

  <\/SPAN><<\/SPAN>runtime<\/SPAN>><\/SPAN><\/P>\n

    <\/SPAN><<\/SPAN>assemblyBinding<\/SPAN> <\/SPAN>xmlns<\/SPAN>=<\/SPAN>“urn:schemas-microsoft-com:asm.v1<\/SPAN>“><\/SPAN><\/SPAN><\/P>\n

      <\/SPAN><<\/SPAN>dependentAssembly<\/SPAN>><\/SPAN><\/P>\n

        <\/SPAN><<\/SPAN>assemblyIdentity<\/SPAN> <\/SPAN>name<\/SPAN>=<\/SPAN>“System.Web.Extensions<\/SPAN>“ <\/SPAN>publicKeyToken<\/SPAN>=<\/SPAN>“31bf3856ad364e35<\/SPAN>“\/><\/SPAN><\/SPAN><\/P>\n

        <\/SPAN><<\/SPAN>bindingRedirect<\/SPAN> <\/SPAN>oldVersion<\/SPAN>=<\/SPAN>“1.0.0.0-1.1.0.0<\/SPAN>“ <\/SPAN>newVersion<\/SPAN>=<\/SPAN>“3.5.0.0<\/SPAN>“\/><\/SPAN><\/SPAN><\/P>\n

      <\/SPAN><\/<\/SPAN>dependentAssembly<\/SPAN>><\/SPAN><\/P>\n

    <\/SPAN><\/<\/SPAN>assemblyBinding<\/SPAN>><\/SPAN><\/P>\n

  <\/SPAN><\/<\/SPAN>runtime<\/SPAN>><\/SPAN><\/P>\n

 <\/P>\n

Important: <\/B> <\/SPAN>For this configuration to work, ASP.NET AJAX 1.0 must also be installed to the machine.<\/P>\n

 <\/P>\n

The bindingRedirect only applies at runtime, so at design-time the third-party component will still be referencing System.Web.Extensions 1.0.  <\/SPAN>As a result, you may encounter the following issues:<\/P>\n

 <\/P>\n

\u00b7         <\/SPAN><\/SPAN><\/SPAN>If the third-party component is an ExtenderControl, it will not get the VS 2008 ExtenderControl designer enhancements.<\/P>\n

\u00b7         <\/SPAN><\/SPAN><\/SPAN>You will not get intellisense for references to scripts inside the third-party assembly.<\/P>\n

\u00b7         <\/SPAN><\/SPAN><\/SPAN>You may get this warning when building your site: \u201cAssuming assembly reference ‘System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ matches ‘System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’, you may need to supply runtime policy.\u201d<\/P>\n

 <\/P>\n

Conclusion<\/SPAN><\/B><\/P>\n

Your Website is now completely upgraded and ready to take advantage of ASP.NET AJAX 3.5!<\/P>\n

 <\/P>\n

 <\/P><\/FONT><\/SPAN><\/SPAN><\/p>\n","protected":false},"excerpt":{"rendered":"

8\/10\/2007 UPDATE:  This blog post was edited to include simplified instructions to work around a known issue w\/ Multitargeting support in VS 2008 Beta 2.  See \u201cMachine Prerequisites\u201d below.   Microsoft Visual Studio 2008 Beta 2 is finally released, and with it comes a bunch of great new features for writing and maintaining ASP.NET AJAX […]<\/p>\n","protected":false},"author":404,"featured_media":58792,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[197],"tags":[4,7279,31,7262,7273,7272,147,7267,7268,7269],"class_list":["post-4934","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aspnet","tag-net","tag-ajax","tag-asp-net","tag-development","tag-orcas","tag-tips-and-tricks","tag-visual-studio","tag-vwd","tag-web","tag-web-2-0"],"acf":[],"blog_post_summary":"

8\/10\/2007 UPDATE:  This blog post was edited to include simplified instructions to work around a known issue w\/ Multitargeting support in VS 2008 Beta 2.  See \u201cMachine Prerequisites\u201d below.   Microsoft Visual Studio 2008 Beta 2 is finally released, and with it comes a bunch of great new features for writing and maintaining ASP.NET AJAX […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/4934","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/users\/404"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/comments?post=4934"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/posts\/4934\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media\/58792"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/media?parent=4934"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/categories?post=4934"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/dotnet\/wp-json\/wp\/v2\/tags?post=4934"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}