Custom document libraries cannot be email enabled

If you create custom document libraries which are not of the type=101 then you cannot email enable these document libraries. We did some research with reflector to find out why:

When SharePoint checks if a template can be email enabled it checks "SPList.ServerTemplateCanReceiveEmail". If we look at the code of that function we can see that email enabled lists are not supported on Meeting Workspaces and that the templateType is checked trough "SPEmailHandler.HasHandler(templateType)"

If we look at the code of "HasHandler" we can see that only 4 listtemplates can be email enabled : Announcements, Events, Document Libraries and Posts (blog).

And we are not so happy with that ... We will need to go for a workaround ...

The count of files and folders in SharePoint 2007 is different then SharePoint 2003

Someone mentioned this already?

This is a Sharepoint 2003 document library with 3 files and 2 folders:

This is a SharePoint 2007 document library with 3 files and 2 folders:

Let's have a look at the "View All Site Content" and "Documents and Lists"

Sharepoint 2003 indicates 5 documents
Sharepoint 2007 indicattes 7 documents

Conclusion : Sharepoint 2007 also counts the folders AND subfolders in his totals! So after an upgrade to Moss 2007 don't panic if you have more files in SharePoint 2007 then SharePoint 2003.

Is this a bug or a new feature ??

For me the SharePoint 2003 approach was much better !

Social Networking in SharePoint 2007

Some time ago a client asked me, "Can you install Social Networking for me?" My first thought was, oh my god, i work with SharePoint 2007 since beta 2 and i have never seen this feature!

I did some research on this topic and saw that i already was using it but never heard from the term Microsoft was using.

In short what is Social Networking in SharePoint?

• My Sites : the personal site for each user with a public and a private part.
  
• The Collegues webpart : The colleagues list is a presentation of other organization members that the specified user works closely with in terms of organizational structure, interaction (i.e., email conversations and instant messaging contact lists) and group/site memberships
  
• The Collegue tracker webpart : The colleague tracker web part allows organization members to privately view their list of compiled colleagues and to modify their views and inclusion in their colleagues list
  
• SharePoint Sites, Links, and Membership Web Parts : These web parts provide the ability for users to view their own Office SharePoint Server site, group and mail list memberships and links as well as those that they have in common with others
  
• In Common With Web Part : Office SharePoint Server provides a summary view of information relating to the memberships, organizational managers and colleagues that a visitor has in common with the owner of a My Site.
  
• Presence Information : When coupled with Office Communications Server and Exchange Server, presence information indicating online instant messaging status, Out of Office messages and contact information is displayed whenever user information is presented (i.e., colleagues and colleague tracker web parts, etc.).
  
• People Search : as you can search on documents you can also search on people in your company/intranet. You can also search on the user profile properties like interests, function, ...

If you are interested in more, i can advise this nice post on the Microsoft SharePoint Blog:
http://blogs.msdn.com/sharepoint/archive/2007/10/24/enabling-and-managing-social-networks-for-business-use-with-microsoft-office-sharepoint-server-2007.aspx

WSS 3.0 SP1 and SharePoint Server 2007 SP1

The SharePoint Product Group has already posted some information about the upcomming Service Pack 1 for WSS 3.0 and Moss 2007.

You can read the full preview here, but these are the highlights:

- Support for Windows Server 2008
- Support for AJAX in SharePoint
- Some new stsadm command line commands
- Serveral hotfixes for wSS 3.0 and Moss 2007

Sharepoint 2003 upgrade to Moss 2007 takes a lot of diskspace

For one of my clients I'm currently migrating there old SharePoint 2003 Portal to the new Moss 2007 environment.

We are using the gradual upgrade procedure, this is the most safe procedure but also uses a lot of diskspace.

I did an upgrade of a WSS site of 32 GB, I monitored the diskspace usage:

• 32 GB for the content database datafile
• 41,4 GB for the content database logfile
  
• 82,8 GB for the temp datafile
• 42 GB for the temp logfile

TOTAL = 198,20 GB for an upgrade of 32 GB

That's "orginal content" x 6,19 = "diskspace needed for the upgrade"

So be sure you have enough diskspace before you start your upgrades!

After the upgrade the temp db is automaticaly deleted and you can shrink the log file of the content database on the SQL Server to free up some diskspace.

My First Blog Post ever !

Hello World !

This is my first blog post ever (yes it's a shame, I know)

Who am I? My name is Bart Vandenheede, 27 years old and I live in Anzegem, this is a small town nearby Waregem, Kortrijk in Belgium.

I'm currently working as a SharePoint Consultant for Dolmen, one of the biggest IT companies in Belgium. Dolmen is one of the first Microsoft Gold Certified Partner for Information Worker Solutions.

So you can already guess the main subjects of this blog?

• Microsoft Office Sharepoint Server 2007
• Windows Sharepoint Services 3.0

I already past the SharePoint exam 70-630, so I can call myself
"Microsoft Certified Technology Specialist: SharePoint Server 2007, Configuring".