Note: 16.Enable workflow looping in SharePoint Designer, eliminating the need for the Visual Studio development environment for that function.

Well, at last! Our Action Pack (see here) has been providing a work around for a number of years, but a platform supported solution is most welcome.

The “App” support section is perhaps the most interesting here, particularly since it can be scoped at the organization level.

Also , the ability to have custom SQL Server databases for these Apps is very important. Even with the SharePoint 2010 list relationship features using multiple SharePoint lists doesn’t really compare to relational database functionality.

Of course, this is all pure conjecture…

http://blogs.msdn.com/b/russmax/archive/2010/03/20/sharepoint-2010-provisioning-user-profile-synchronization.aspx

And for SP1 for SharePoint Server (Enterprise and Standard) information http://support.microsoft.com/kb/2460045. Download from: http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26623

While useful, the user interface is not particularly polished or easy to use. In particular, the SharePoint Diagnostic Studio must be run with the language set to “US-English”, otherwise date formats will be presented incorrectly and date/time filtering will not work.

Overall Description: http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=971

Download from: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=718447d8-0814-427a-81c3-c9c3d84c456e&displaylang=en

Documentation: http://technet.microsoft.com/en-us/library/hh144782.aspx

• CAML Builder from U2U (http://www.u2u.be/Res/Tools/CamlQueryBuilder.aspx): Build and test your CAML queries and paste into your code.
• CKS (Community Kit for SharePoint, Tools Edition) (http://cksdev.codeplex.com/ ): Makes the SharePoint development cycle tolerable (almost). Version 2 was released May 2011.
• ULS Viewer (http://archive.msdn.microsoft.com/ULSViewer ) In my opinion, the best.
• SharePoint Manager (http://spm.codeplex.com/). Invaluable for browsing a SharePoint farm, viewing and changing parameters and option.

For uploading single or groups of files from the desktop or mail messages from Outlook I use, of course, our “SPDrag&Drop” tool. Take a trial by downloading from here: http://www.nickgrattan.net/SPDragDrop/ProductInfo.aspx

SPList spWPG = spWeb.Lists["_catalogs/wp"];  // does not work

 Instead, you need to use the following code:

SPList spWPG = spWeb.Lists["Web Part Gallery"];

Reference: http://meiyinglim.blogspot.com/2007/10/programatically-organizing-web-parts-in.html

• App_GlobalResources folder in the VirtualDirectories folder in inetpub (e.g. C:\inetpub\wwwroot\wss\VirtualDirectories\80)
• Resources folder in the 14 hive (e.g. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\Resources)
• Config/Resources folder in the 14 hive (e.g. C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\Resources)

In general, a single resx file in your solution should be copied into each of these locations during installation.  This is how they are used:

• Resources files in App_GlobalResources are used when code in an ASPX page refers to a resource, e.g.

<asp:Label ID="lblNumberingTitle" runat="server" Text="<%$Resources:GlobalSiteResources, AutoNameTitle %>" />

• Resources files in the Resources folder are used when referencing resources using the SharePoint object model, e.g.

btnExport.Text = SPUtility.GetLocalizedString("$Resources:GlobalSiteResources, Tab_Export", "GloablSiteResources", language);

• Resources files in the Config/Resources are copied into the App_GlobalResources folder whenever a new web application is created. By adding the resx files here you will ensure your application will be able to access its global resource files in new web applications.

The links cannot be hidden through the web part configuration user interface. Instead you need to:

1. Open the ASPX page in Microsoft SharePoint Designer 2010.
2. Locate the Chart Web Part in Code View.
3. Edit the ShowToolbar property from “True” to “False”.
4. Save changes.

Now these links will be hidden. You can use the standard drop down web part menu to access them if you need to without re-enabling them: