In a previous post about the AJAX Extensions, I detailed the copy commands to retrieve the DLLs from the GAC. Same thing, this time for the ASP.NET 3.5 Extensions. If you are demoing CTP material in a hosted environment, you will likely need these in your app's bin to avoid the inevitable configuration error.

copy "C:\WINDOWS\assembly\GAC_MSIL\System.Web.Extensions\3.6.0.0__31bf3856ad364e35" C:\dev\MMVCApp\bin
copy "C:\WINDOWS\assembly\GAC_MSIL\System.Web.Extensions.Design\3.6.0.0__31bf3856ad364e35" C:\dev\MMVCApp\bin

A great series of blog posts by Scott Guthrie about the ASP.NET MVC Framework coming soon as part of the ASP.NET 3.5 Extensions release.

Upon hearing the news, a few friends started questioning its intent, usefulness, and longevity. Many of us have been using or contemplating conversion to the MVP pattern, most recently using WCSF. The recent split of the MVP pattern by Fowler has caused many believers to question their faith. While many are still "proving" MVP, MVC has been around for nearly 30 years. Some believe that MVP and MVC can co-exist. Here is a comparison of MVP and MVC that concludes by painting an optimistic picture of MVP and MVC contributing to each other.

ASP.NET MVC appears to be the answer to my unit testing, REST, and code separation prayers. Thank you ScottGu and team!

Check it out!

Here is a fantastic solution to a common ORMr problem seen when regenerating code that overwrites changes made to previously generated and more recently manually-modified code.

http://weblogs.asp.net/scottgu/archive/2007/11/19/visual-studio-2008-and-net-3-5-released.aspx

I'm downloading it now.

It's only a week away, and there are still spaces left.

Information   Register    Sessions

Check out this mess.   I would like to see any one of the many people commenting to show one scrap of evidence to support their side of this issue.   All I see is "I read in an article that this was bad", "M$ said this is true", and my favorite argument "because that's what I think".   Great arguments for the third grade audience.   People... please try to prove something here with some real evidence.

I happen to believe stored procedures are the way to go because Elvis landed in a spaceship in my front yard and told me to only use stored procedures.

http://weblogs.asp.net/fbouma/archive/2003/11/18/38178.aspx

The CaptchaImage images and comments worked fine on my local machine.   With no difference in settings or permissions, my site threw javascript errors when saving comments, and the CaptchaImage images failed to appear.   I tried to research it, but found only one person that claimed to have the same issue with no resolution.

I read many posts saying that using dasBlog 1.9.6264.0 on 2.0 Framework had serious issues.   I couldn't believe what I was reading since everything was working fine in 2.0 on my local machine, and only the comments were failing on my site.   I changed the app to use the 1.1 Framework and made the required web.config changes.   The result: add two more items to the list of things that don't work on dasBlog 1.9.6264.0 with 2.0 Framework.

Look ma, comments are working!

Many hosting companies, like mine, won't have the AJAX Extensions installed in the GAC for quite a while, if ever.   No worries, you can just put the DLLs in your Bin folder.   Since MS hasn't graced us with the DLLs, so you'll have to get them out of your GAC.  I haven't found a way to copy DLLs using Windows Explorer, but command-line never fails.

copy "C:\WINDOWS\assembly\GAC_MSIL\System.Web.Extensions\1.0.61025.0__31bf3856ad364e35" C:\dev\MyApp\Bin\
copy "C:\WINDOWS\assembly\GAC_MSIL\System.Web.Extensions.Design\1.0.61025.0__31bf3856ad364e35" C:\dev\MyApp\Bin\

I frequently place an UpdatePanel around a paged GridView with inline editing.   During OnRowUpdating, the object is saved.   If the save was not successful, I like to show an alert box with the error message.  

I recently migrated from the Atlas May CTP to ASP.NET 2.0 AJAX.   The following code worked with the May CTP, but, from my research, has not worked since July CTP:

Page.ClientScript.RegisterStartupScript(typeof(string), "alertScript", "alert('Error Message');", true);

However, our pals at Microsoft have given us something just as good.   I found it by mistake while trying to put in a hack involving checking the value of ScriptManager.GetCurrent(Page).IsInAsyncPostBack.  Here is the AJAX-friendly equivalent:

ScriptManager.RegisterStartupScript(this.updatePanel, typeof(string), "alertScript", "alert('Error Message');", true);

Hope this helps someone.  There are many blog posts, with many more comments, with people compaining about this.