I am looking at my site over to .NEt 3.5 so that other parts of my site can take advantage of the new features. Anyone tested BV5 (SP2 or SP3) on .NET 3.5.

Rick

Thanks Marcus. I presume that you compiled SP3 under .NET 3.5 not SP2. I would assume the the globalization coding issues that caused errors in SP2 and prevented SP2 from working with AJAX might crop up with the same globalization errors now that AJAX is part of .NET 3.5

Marcus, I was referring to the errors coming up in BV5 SP2 when using Microsoft AJAX as described in http://forums.bvcommerce...46406&g=49332#m49332

Marcus, if you look at the post I referenced above that was not the issue. I wasn't using MS AJAX within BV5, which as you said is not supported, but I have other parts of my site where I wanted to use Microsoft's AJAX. Pre-SP3 code had inconsistent use of globalization calls which, if you added AJAX to the site, caused major errors in BV5 all of which were referenced in the post above. I documented all of the files in SP2 and earlier that had the incorrect globalization calls. I ultimately had to remove all the references to MS AJAX in the root web.config of my site in order for BV5 SP2 to work. I presume that this would also be the case with SP2 running under .NET 3.5 because all of the AJAX references have been simply moved into the runtime.

The discussion at the time from myself and others was that MSs AJAX was that many of us would want to use this mainstream AJAX technology which is why the globalization calls on BV5 needed to be changed.


Rick

All of the Globalization calls are qualified in BVC5 SP3 so there is no ambiguity (the problem in SP2).

If you convert your site to 3.5 using VS2008 (which should add the reference to Web.Extensions where MS Ajax lives and update your web.config) you can use MS Ajax in the site. 3.5 is just 2.0 with some extensions. Few web hosts have added the extensions to shared servers, but I suspect that will change quickly.

I don't think you should put Anthem controls inside of an MS UpdatePanel or visa-versa. But they work side-by-side on the same page just fine. The individual Anthem controls (like Anthem.DropDownList or Anthem.Label) result in much smaller updates than MS UpdatePanel. If I used both libraries, I would use Anthem for fine-grained stuff and MS Ajax for the fancy add-on controls (DialogBox, etc).

But I tend to like Anthem + YUI Library instead. YUI works with more browsers than the MS Ajax Control Library and you don't have to modify the site in any way (YUI is all javascript which Yahoo will host for you if you want).