Quite often you will need to get selected values from a Multiple-Selection list box to a field. I haven’t found a way to do in rules but the following code will solve the problem.

Suppose you have a Multiple-Selection List Box named myListBox on an InfoPath form and an after change event to fill a Text Box named myTextBox with the values or display names of the items that were selected in the Multiple-Selection List Box.

Retrieving the values of selected items
You could use the following C# code to retrieve the values that were selected:

        public void field13_Changed(object sender, XmlEventArgs e)
        {
            XPathNavigator root = MainDataSource.CreateNavigator();
            XPathNodeIterator iter = root.Select("//my:myListBox ",
              NamespaceManager);

            System.Text.StringBuilder sb = new System.Text.StringBuilder();

            while (iter.MoveNext())
            {
                string value = iter.Current.Value;
                sb.Append(value);
                if (sb.Length > 0)
                {
                    sb.Append(";");
                }
            }

            root.SelectSingleNode("//my:myTextBox",
              NamespaceManager).SetValue(sb.ToString());
        }

Retrieving the display names of selected items

If you want to retrieve the Display Names of the items that were selected and you’ve bound the Multiple-Selection List Box to a repeating node either in the Main data source or a secondary data source, you’ll have to do a programmatic lookup to retrieve the Display Names.

You could use the following C# code to retrieve the display names of the items that were selected:

XPathNavigator root = MainDataSource.CreateNavigator();
XPathNodeIterator iter = root.Select("//my:myListBox",
  NamespaceManager);

System.Text.StringBuilder sb = new System.Text.StringBuilder();

while (iter.MoveNext())
{
  string value = iter.Current.Value;

  XPathNavigator secDS = DataSources["Fruits"].CreateNavigator();
  string displayName = secDS.SelectSingleNode(
    "/dfs:myFields/dfs:dataFields/d:Fruits[@ID = '"
    + value + "']/@Name", NamespaceManager).Value;

  sb.Append(displayName);
  sb.Append(";");
}

root.SelectSingleNode("//my:myTextBox",
 NamespaceManager).SetValue(sb.ToString());

where Fruits is a secondary data source, @ID the value of an item, and @Name the display name of an item.

Note: You cannot do a lookup for items if you’ve manually entered them into the list box.

More useful code you can find from http://www.bizsupportonline.net/blog/2009/03/programmatically-retrieve-selected-items-multiple-selection-list-box-infopath/

Sometime you may find Site.RootWeb.AllUsers didn’t return all users even the user you can find in search. This is because AllUsers shows active users, i.e. those who have interacted with the sitecollection at least once. A quick way to add user in is go to your site collection level (top-level Web site ), clcik advanced permission, then add users in then removed them.

Quite often you need to find which stored procedure contains key word. I find this blog and use
SELECT ROUTINE_NAME, ROUTINE_DEFINITION
FROM INFORMATION_SCHEMA.ROUTINES
WHERE ROUTINE_DEFINITION LIKE '%foobar%'
AND ROUTINE_TYPE='PROCEDURE'

It happens when you are trying to delete a SQL user. To change the DB_Owner to some another “Database Principal”; simply Drill Down to your Database in Sql Server Management Studio and further more Drill Down to your_DB_Name >Security > Schemas > db_owner > right click > select properties. You would find the name of the “Database Principal” that you want to delete. Change this to some another “Database Principal”; for Example, to “dbo”.
You need to make the same changes to all the schemas where the “Database Principal” is having/owning the role. For Example, if it is having “db_owner, db_datareader, db_datawriter” roles; then you have to make the above said changes for all these 3 schemas.

If you create a custom viewer and add in your web.config.

<add key="ReportViewerServerConnection" value= ...>

You will find your Site Ussage report will not working and throw error with your assembly does not implement IReportServerConnection or could not be found. After searching the net and I found Steve’s blog. Although the error is different, the fix is the same.

“The problem is that web config’s are inherited in IIS therefore the reporting services web service web config settings are inherited from the report manager web config which means that the setting you removed is needed for report manager but breaks the web service.”

So to fix the problem, go to C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\TEMPLATE\LAYOUTS and open web.config, add:

<appSettings>
    <add key="ReportViewerServerConnection" value="" />
</appSettings>

I found the easiest way to add custom page to SharePoint is to create a host aspx page and embed usercontrol inside, so next time if you have any update you can just update the usercontrol.

Below is the aspx inline page and I upload to Pages library

<%@ Page Language="C#"  EnableSessionState="true"  MasterPageFile="~masterurl/default.master"%>
<%@ Register src="~/_controltemplates/TestUserControl.ascx" tagname="TestUserControl" tagprefix="uc1" %>

<asp:Content ID="Content2" ContentPlaceHolderID="PlaceHolderMain" runat="server">
<asp:ScriptManager ID="ScriptManager1" runat="server"/>
      <uc1:TestUserControl ID="JDEGLSearch" runat="server" />
</asp:Content>

The TestUserControl.ascx just a User Control created in the visual studio. You can add the ui into 12\TEMPLATE\CONTROLTEMPLATES

or you can add into _\12\TEMPLATE\LAYOUTS folder but which means everyone can access the page

<%@ Page language="C#" MasterPageFile="~/_layouts/application.master" Inherits="Microsoft.SharePoint.WebPartPages.WebPartPage,Microsoft.SharePoint,Version=12.0.0.0,Culture=neutral,PublicKeyToken=71e9bce111e9429c" %>

<asp:Content ID="Content2" ContentPlaceHolderID="PlaceHolderMain" runat="server">
  <b>Hello</b>
</asp:Content>

If you received this error when use session in your custom aspx page deployed to SharePoint:

Session state can only be used when enableSessionState is set to true, either in a configuration file or in the Page directive. Please also make sure that System.Web.SessionStateModule or a custom session state module is included in the \\ section in the application configuration.

If you add “EnableSessionState=”true” “ to your it should enable it but also you need to modify you web.config

The problem is that by default, Sharepoint does not allow server side code in .aspx pages by default. You need to enable this using PageParserPath. Add the PageParserPath inside of the PageParserPaths node of the web.config file, changing the virtual path to the path you want to enable. Or you can use /Pages/* as the value if they are in the same folder

The server-packages of October 2009 Cumulative Update for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 are ready for download. October 2009 Cumulative Updates introduce more rules on Pre-Upgrade Checker, which can help customers to prepare the upgrade of their SharePoint farm to SharePoint 2010.

Download Information

Windows SharePoint Services 3.0 October 2009 cumulative update package
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=974989

Office SharePoint Server 2007 October 2009 cumulative update package
http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=974988

Detail Description

Description of the Windows SharePoint Services 3.0 October 2009 cumulative update package
http://support.microsoft.com/kb/974989

Description of the Office SharePoint Server 2007 October 2009 cumulative update package
http://support.microsoft.com/kb/974988

Installation Recommendation for a fresh SharePoint Server

To keep all files in a SharePoint installation up-to-date, the following sequence is recommended.

1. Service Pack 2 for Windows SharePoint Services 3.0 and language packs
2. Service Pack 2 for Office SharePoint Server 2007 and language packs
3. October 2009 Cumulative Update package for Windows SharePoint Services 3.0
4. October 2009 Cumulative Update package for Office SharePoint Server 2007

Please note: Start from April 2009 Cumulative Update, the packages will no longer install on a farm without a service pack installed. You must have installed either Service Pack 1 (SP1) or SP2 prior to the installation of the cumulative updates.

After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or “psconfig -cmd upgrade -inplace b2b -wait” in command line. This needs to be done on every server in the farm with SharePoint installed.

The version of content databases should be 12.0.6520.5000 after successfully applying these updates.

You can also refer to April Cumulative Update post for deployment guides, slipstream how-to links and FAQs.

Sometime you get this error when you deployed a web part which use references. To fix the problem, you need to open your aspx page and add references like , even you are not useing it in your UI

Finally today, I managed to install TFS 2010 on my virtual pc which is server 2008 with SharePoint 2007. The erors I got is all aournd permission. So you need to make sure your SharePoint Service and Application Pool use domain account. There are 2 problems I had;
1. Ther error happens when configure the TFS.
TF255275: The following Web service for SQL Server Reporting Services could not be accessed: http:///ReportServer/ReportService2005.asmx.
To fix this error, you will need to remove the ReportServer and ReportServerTempDb database from the database server, see here for more details.
2. Grant TFS permission to SharePoint. This is a permission problem. I will need to change all my sharepopint service to run under domain account. See here