Contact
Send mail to the author(s) Email Me

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

Sign In
Navigation

Tag Cloud
.NET Framework (31) AJAX (9) ASP.NET (16) ASP.NET MVC (3) C# (32) Cloud (2) Database (6) Dev Community (2) Dev Tools (5) Enterprise Library (1) Futures (2) General (6) Javascript (7) LINQ (2) Mobile (1) MSDTC (5) Quotes (3) SQL (3) Transactions (4) WAS (2) WCF (19) WIF (1) Visual Studio (3)

Archive
<February 2010>
SunMonTueWedThuFriSat
31123456
78910111213
14151617181920
21222324252627
28123456
78910111213

Categories

Blogroll
Home Feed your aggregator (RSS 2.0)
# Wednesday, February 07, 2007

I just migrated from the Atlas July CTP to ASP.NET 2.0 AJAX Extensions 1.0.  After following all of the instructions on the AJAX site, my web site still showed tons of errors.  I'm using a Web Site, not Web Application, with a ScriptManager in a WebForm that uses a MasterPage.   Every page shows errors on AJAX tags. 

Yes, I removed the Atlas DLL.  No, my web.config is not messed up.  Something else is wrong here.   I found a "fix".   The sequence of steps seems a little odd to me, but I did't care, it worked.  However, the problem resurfaced when I closed my MasterPage.

More searching led me to a great alternative to a true solution.   An ASP.NET Forums post had some back-and-forth on the topic.  Ultimately, the best solution at this point is to change the tagprefix to "ajax".   This works great, and, in fact, I like it better because it separates the ajax controls from the standard asp controls.

<add tagPrefix="ajax" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>

Wednesday, February 07, 2007 9:34:09 PM (Eastern Standard Time, UTC-05:00)  #    Comments [0]   AJAX | ASP.NET  | 
Comments are closed.
Copyright © 2010 Scott Klueppel. All rights reserved.