This post is liberally linked into other very good resources – I only offer it as a help or path through some of the options. The ‘lazy’ web.config reconfigure via Visual Studio framework switch is very effective. I did it manually on a test system and had a lot of control reference problems. I will be trying it again to better understand what I missed though this time with a web.config to run a diff against.

Install Net Framework 3.5 SP1

Web.Config Setup

1. Backup site web.config
2. Create a 2.0 web app in VS
3. Copy in web.config
4. Change target framework to 3.5 and save web.config over production.
5. Reference: http://weblogs.asp.net/jan/archive/2008/10/10/enabling-net-3-5-in-sharepoint-2007-sites-the-lazy-way.aspx

Add safe control in <Sharepoint><SafeControls> make sure it is 3.5.0.0 (if 3.5 SP1 installed)

1. Reference: http://sharepoint.microsoft.com/blogs/mike/Lists/Posts/Post.aspx?ID=3  (see Point 6 )
2. Reference: http://www.codeproject.com/KB/sharepoint/MossAjaxWebPart.aspx?display=PrintAll&fid=417786&df=90&mpp=25&noise=3&sort=Position&view=Quick&select=2156594

Default.Master

1. Add SPScriptManager to (default) master page via SPD (Sharepoint Designer)  – here is where to place it.

 <form runat=”server”>

<WebPartPages:SPWebPartManager runat=”Server” />

<asp:ScriptManager runat=”server” ID=”ScriptManager1″>

</asp:ScriptManager>

<TABLE class=”ms-main” CELLPADDING=0 CELLSPACING=0 BORDER=0

WIDTH=”100%” HEIGHT=”100%”>

SPD designer gives a IE 6 warning ?? ignore it

Ajax Web Part

1. Deploy a simple Ajax Web Part
2. Reference: http://jamestsai.net/Blog/post/How-To-Create-AJAX-enabled-SharePoint-Web-Part-with-UpdatePanel-and-UpdateProgress-in-10-minutes.aspx