Sharepoint : Default Maximum File Upload Size Limit Allowed

By default, Sharepoint allows a maximum file size of 50MB that can be uploaded into any document libraries, list attachment and etc. The default file upload size can be changed at Central Administration > Application Management > Web Application General Settings > Maximum Upload Size. By doing this, users will be able to upload a larger file size into Sharepoint.

After changing the maximum file size, you may want to consider increasing the IIS Connection Time Out setting. By default, the IIS connection time-out setting is 120 seconds.

Sharepoint 2010: Asset Library Supported Video Format or File Type

In Sharepoint 2010, Asset Library is a new feature that allows you to upload Video, Audio and Images. It is exciting that Sharepoint finally has a built in Silverlight video player. Unfortunately, it only supports a very limited list of file format or file type, particularly WMA format and some unknown formats. A list of the supported format can be viewed here: http://msdn.microsoft.com/en-us/library/cc189080%28VS.95%29.aspx

To solve this problem, a third party solution can be used such as Bamboo's Sharepoint Video Library.

Another solution for better streaming capability is to use a 3rd party FLV player.

Sharepoint and Lotus Notes Integration

There are many enterprise clients looking for Lotus Notes integration with Sharepoint, such as viewing Sharepoint Calendar in Lotus Notes Client, or Viewing Lotus Notes Calendar in Sharepoint. However, based on my research, there is only web part available to view Sharepoint Calendar from Lotus Notes Client, but not the other way round. One major provider for this integration is Main Soft. For those who want to view Lotus Notes email or calendar from Sharepoint, too bad and sorry, but there is none.

The only integration with Lotus Notes is to browse the Sharepoint Calendar from Lotus Notus Client. I wish there is some solutions to this requirement.

Sharepoint 2007: C# Building Dynamic SPQuery to Query a Sharepoint List

If you are developing a Sharepoint page or Sharepoint web part which requires writing or constructing dynamic SPQuery or query, such as a Search Criteria page where users can choose to enter one or more search criteria. You can use Caml.cs to construct the SPQuery dynamically. The following example shows you how you can write you dynamic SPQuery using caml.cs helper class.

The following example shows how you can generate dynamic query.

//Build Search String Query 
//Product ID
if (strProdID != "")
    clauses.Add(Caml.Eq("" + strProdID + ""));
//Product Name
if (strProdName != "")
    clauses.Add(Caml.Contains("" + strProdName + ""));
//Product Classification
if (strProductClassification != "0")
    clauses.Add(Caml.Eq("" + strProductClassification + ""));
//Division
if (strDivision != "0")
   clauses.Add(Caml.Eq("" + strDivision + ""));
//Product Manager
if (uvcProdManager.Count != 0)
    clauses.Add(Caml.Eq("" + uvcProdManager[0].User.ID.ToStringSafe() + ""));

//append where 
if (clauses.Count != 0 )
    query.Query = Caml.Where(Caml.And(clauses));
query.Query += Caml.OrderBy("ID", false);

Sharepoint 2007 Site Membership Web Part

We have often encountered the issue whereby the SiteMembership web part in Sharepoint 2007 does not display any site memberships at all. It is always blank at the time. I couldn't find out the reason for this unexpected behavior. Thus, I have built my own Site Membership web part to replace the OOTB SiteMembership web part.

You may download the source code here

SharePoint 2010: User Profiles - You receive an error - "An unexpected error has occurred." when you try to browse to the page to Manage a User Profile

In Sharepoint 2010, User Profile Service Application is a new service that replaced the SSP. I encountered ""An unexpected error has occurred." error when I selected a user and click on Edit, and also when I wanted to edit  User Profile Properties. The page was working correctly without any problems previously. Due to some unknown reasons, the user profile service application failed and was throwing me this error page.

This is an expected behaviour if the User Profile Synchronization Service is started on the SharePoint server hosting Central Administration. To fix this issue, simply perform a recycle of IIS Central Administration Application pool is required to get this working.