Check out this great site that is designed to help .NET Developers to learn to build solutions with SharePoint: http://MSSharePointDeveloper.com

·         User Management

The site includes some great info, such as:

·         An Introductory Whitepaper

·         Benefits of SharePoint for Developers

·         A SharePoint VPC

·         Hosted MSDN Virtual Labs in C# and VB.NET

·         Video Interview with SharePoint MVPs

·         Screencasts

·         Web Casts with SharePoint MVPs

·         Quickstarts

·         Labcasts

·         Presentation Download

·         Hands on Labs Download

·         Additional Resource Links

Check it out!  http://MSSharePointDeveloper.com

I get a lot of questions regarding the use of SharePoint as a solutions platform. I personally think it's a great tool for many (but not all) applications. The reason?  SharePoint lends something that we like to call the "productivity tier," which is missing from most platform architecture stacks.  We're all used to the UI tier, application tier, and data tier.  Those three, however, fail to address a common requirement, which is being able to accomodate things like frequent changes to business processes, human workflows, tie-in with unstructured information, and data or visualization mashups that an end-user might want to create.  SharePoint can help with all of those scenarios.

So let's say you're going to use SharePoint as your platform. Then the main question I get is "give me a methodology for team-based SharePoint development that combines custom code that I write and content that will be managed inside of SharePoint".

To that end, here's a great doc:  http://www.microsoft.com/downloads/details.aspx?FamilyId=65F21935-CBC0-4178-8C08-4C56F721C87D&displaylang=en

The document suggests implementation scenarios, tools, and development environments for SharePoint-based solutions.  It's quite handy.

Take a look and let me know what you think.

Now that MOSS 2007 has been out for a while, I'm getting a lot of requests for deeper knowledge and guidance. In that regard, I’m pleased to announce that we've recently released Advanced SharePoint videos and whitepapers on TechNet.

The SharePoint team has released post-SP1 hot-fix rollups for both WSS and MOSS. If you haven't installed SP1 yet, be sure to take some time to plan your deployment. And then review and install these rollups:

WSS Post-SP1 Rollup:  http://support.microsoft.com/kb/941422
MOSS Post-SP1 Rollup: http://support.microsoft.com/kb/941274

One of the most popular requests I see from customers regarding enterprise search is to be able to refine search results by category with a simple click.

The best free way to enhance MOSS 2007 search with this type of feature is via the free faceted search web parts out on codeplex: http://www.codeplex.com/FacetedSearch

Want to check it out?  Here's a live demo: http://www.wssdemo.com/Search/Pages/results.aspx?k=search. Check out the "Search Facets" section on the right.

The new 2.0 release encapsulates foundation changes in the design and code, that provides perfect balance between accuracy and performance.

Highlights:

• Multi-thread processing. 1st thread runs for up to 500 facets synchronously, while the 2nd thread is running asynchronously against up to ~30,000 facets
• Client side refresh (not AJAX) that updates only Facets web part w/o page refresh
• Web part connections to pass Facet settings to the Bread Crumbs
• Extended facet schema now supports:
• Facet icons. Default icon per Facet name complimented by an icon per Facet value
• Friendly names for facet values
• Exclusions. Allow exclude facet when values match pattern
• Built-in wild-card match, especially useful for exclusions
• Improved search syntax, added supports for sentences and quoted phrases

This release includes numerous fixes and complemented by extended documentation.

I just wanted to take a moment to remind everyone about the SharePoint Capacity Planning Tool.

Official description:  The SharePoint Capacity Planning Tool comprises models of both Microsoft Office SharePoint Server 2007 (MOSS) and Windows SharePoint Services 3.0 (WSS) that allow you to explore the necessary infrastructure for either deployment based on usage requirements. This tool uses the System Center Capacity Planner 2007 (SCCP) as an engine to provide for data collection, visualization, simulation, and report writing. The tool can be used in pre-sales and feasibility studies of a deployment project to give you a rough estimate of hardware requirements.

The tool is able to consider variations in usage, size of installation, networking technology, scale, and availability.

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

According to Forrester, 2008 will be the year that Web 2.0 will make it big in the enterprise, with SharePoint being a huge part of it.

Check it out:  http://www.networkworld.com/news/2008/013008-forrester-predictions.html

Many of you are planning to deploy SharePoint SP1, which is a good idea.  There are many, many useful updates and fixes.

For a detailed rundown, make sure you take a peek at this spreadsheet, which lists all of the 2007 Office System SP1 details: http://support.microsoft.com/kb/942390.

I'd also like to give you a few additional tips:

• Install SP1 on a test server to make sure all of your 3rd party and custom web parts and features still work.
• You can't go back. There's no uninstall. Back up everything.
• The farm is down during the upgrade. Plan accordingly.
• For MOSS 2007 servers, you need to install WSS 3.0 SP1 and MOSS 2007 SP1, in that order. At the completion of the WSS 3.0 SP1 installation, you will be prompted to run the SharePoint Products and Technologies Configuration Wizard. DO NOT RUN IT YET. Instead, cancel it and then run the MOSS 2007 SP1 install. Then, manually start the SharePoint Products and Technologies Configuration Wizard.
• If you're installing SP1 on multiple servers, make sure you complete SP1 on all servers in the farm. If some of the servers have SP1 and some don't, your farm won't work.
• After you install SP1, more disk space is required for your query server or index server. If adequate disk space is not available, your query servers will slow down or stop. This issue occurs because the method used to merge indexes has been modified to significantly improve performance and reduce server downtime. However, this change increases the disk space required to perform a master merge. Previously, a maximum of 2 times the physical size of the index was required. The new maximum disk space requirement on a query server or index server is increased to 2.85 times the physical size of the index.
• If you are using the Content Editor Web Part on a MOSS 2007 Web server that offers languages other than the installed language, users will receive a script error when they use the Web Part. You can prevent this issue by installing the Windows SharePoint Services 3.0 Service Pack 1 Language Template Pack.
• You may get an error related to orphaned objects in one of your content databases. SharePoint requires a clean environment going forward. Here's some information on orphans: http://blogs.technet.com/corybu/archive/2007/05/31/sharepoint-orphans-explained.aspx

Happy upgrading!

You've probably already heard, but wanted to make sure everyone was aware that Office 2007 SP1 (including WSS 3.0 SP1 and MOSS 2007 SP1) went live on microsoft.com this week and is now available for download.

The link for all of the SharePoint downloads (and more info) is here: http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx

There are over 600 specific bug fixes across the Office server products alone - make sure you put a plan in place to upgrade.

Additional information:

·         MOSS SP 1 Fixlist KB - http://support.microsoft.com/?id=942390

·         MOSS SP 1 Description KB - http://support.microsoft.com/?id=936984 

·         WSS SP 1 Fixlist KB - http://support.microsoft.com/?id=942388

·         WSS SP 1 Description KB - http://support.microsoft.com/?id=936988

·         How to Deploy SP 1 KB - http://support.microsoft.com/?id=945013

One of the really useful features of MOSS 2007 is the out-of-box usage reporting. However, it's not enabled by default. If you think you'll want to let site collection admins view information about top pages, top users, etc, then make sure you enable it centrally.

In Shared Services, under Office SharePoint Usage Reporting, click Usage Reporting. Then check the Enable advanced usage analysis processing checkbox.

I'm out in Redmond this week speaking at the Strategic Architecture Forum on Composite Applications. I think we'll see more focus on building applications using composite architectures in the future. The idea is to enable reuse at the end-user level...not just at the developer level. I'll talk more about how SharePoint plays a role in composite applications over the next couple of months.

What is SharePointPedia?  SharePointPedia.com is a public-facing social computing application built on top of Microsoft Office SharePoint Server (MOSS) 2007. It's designed to enable users on the Web to find and share content about SharePoint and related stuff.

Anyone with a Windows Live ID can register and submit content recommendations, leave comments, and vote for the best content.

Be sure to check it out!

SharePoint content databases can be any size. There are no hard limits.  There - I've said it.

I hear customers and partners still claiming that there's a 50GB size limit. There is NOT. It's a guideline, not a rule. Let's say you want to store 1TB of data in SharePoint...no problem. You could have 2-3 content databases with 400GB each. Or one very large content database. SQL 2005 and MOSS 2007 would handle that fine.

So why the limit?  Managability. It's simply faster to restore smaller databases.

The 50GB myth comes from a practical limitation that administrators put on themselves; it's simpler and easier to manage a SharePoint environment when databases are small. Many customers I work with still don't have the hardware, people, and time that they need to have a real recovery plan.  Why?  Because in many cases, SharePoint grew out of pure business need and caught on like wildfire. I know large customers who are still running SharePoint like a departmental application. Once they realize that it's a business critical application - at enterprise scale - governance (along with funding) is added to the master plan.  Do you want to convince your manager or business lead (i.e. the one with the budget) that you need more resources?  Shameless plug: get them a copy of my book.  They will understand SharePoint better and realize the need for governance, planning, and better resources for IT.

One more thing: If you're looking for a better way to backup and restore SharePoint, especially for large databases, check out Data Protection Manager 2007. Why? It supports change-only, agent-based backups and single site/single file restore in WSS 3.0 & MOSS 2007.  I'll be doing some testing with large content databases over the next couple of weeks and sharing my results.

In the meantime, here are some great posts by Joel Oleson on database and site collection sizes:

Content Database Size:  http://blogs.msdn.com/joelo/archive/2006/08/01/684691.aspx, http://blogs.msdn.com/sharepoint/archive/2006/08/03/687995.aspx

Site Collection Sizing: http://blogs.msdn.com/joelo/archive/2007/01/31/tips-on-site-collection-sizing.aspx

WSS 3.0 and MOSS 2007 do not need a fix to work with this year's DST changes.

WSS v2 and SPS 2003 need to install the update, http://support.microsoft.com/kb/924881.  The update includes an updated timezone.xml file.

I've gotten a lot of questions about SharePoint limitations lately. SharePoint can scale to hundreds of millions of documents and items and host terabytes of data.

This article (Plan for software boundaries) provides recommendations for acceptable performance: http://technet2.microsoft.com/Office/en-us/library/6a13cd9f-4b44-40d6-85aa-c70a8e5c34fe1033.mspx?mfr=true.

I'll be discussing the myth of the 50GB limit on content databases in my next post.

Ever wish you could get some help on SharePoint but don't know where to turn?  If so, be sure to check out the MSDN SharePoint Community Forums: http://mssharepointforums.com.

I will be monitoring the forums along with MVPs, SharePoint product team members, and the community at large.

I've gotten some questions about using Office SharePoint Server 2007 to crawl websites that use Forms-based Authentication (FBA) or Cookie-based Authentication (CBA). SharePoint Server 2007 supports this functionality with a hotfix. (If you don't have the hotfix installed, only the logon page will be crawled.)

You can download the hotfix here: http://www.microsoft.com/downloads/details.aspx?FamilyId=B3C932A5-B3C0-4473-8EA5-62AE44190878&displaylang=en

Before you install the hotfix, be sure to review this KB article:  http://support.microsoft.com/kb/934577/en-us

In Excel 2003, there was a feature that let you sync changes from an Excel 2003 spreadsheet to a SharePoint List and vice versa. In Excel 2007, this feature was deprecated.  I get asked about the lack of this feature all of the time.

Good news!  Back in June, we published an Excel 2007 add-in that puts this functionality back.  You can get it at: http://www.microsoft.com/downloads/details.aspx?FamilyID=25836e52-1892-4e17-ac08-5df13cfc5295&DisplayLang=en.

There's also a companion MSDN article entitled "Publishing and Synchronizing Excel 2007 Tables to SharePoint Lists": http://msdn2.microsoft.com/en-us/library/bb462636(office.11).aspx

Enabling employees to work with greater agility and with better collaboration tools is a huge theme I'm seeing these days. Many companies are jumping on the Enterprise 2.0 bandwagon, which is taking Web 2.0 and social computing tools and putting them inside of large companies.  What do those tools look like?  In short, they include search, wikis, blogs, experise location, RSS feeds, shared calendars, and real-time communication.

MOSS 2007 hits on all of these (with RTC driven in conjunction with Office Communications Server). I've seen a huge uptake in MOSS 2007 for enabling Enterprise 2.0.

According to this Information Week article (http://www.informationweek.com/news/showArticle.jhtml?articleID=199905440), 45% of companies have workers blogging, 43% use RSS feeds, and 35% of companies have employees using wikis. 

How does your company compare?

Need a MOSS VPC?  Here's a MOSS 2007 VPC (Including the 2007 clients).  The VPC includes the MOSS Product Evaluation Guide (on the desktop) and is configured so the walk through at the end of the guide works with the image.  The catch: it expires after 30 days.