SharePoint 2010

SharePoint History

some interesting words on the history of what is called SharePoint

28 August 2006
SharePoint History

In 2007, Microsoft will release the third version of their SharePoint server product – Microsoft Office SharePoint Server 2007 (MOSS 2007). It will provide a wide variety of features that make it a complete information management platform, capable of delivering solutions for business intelligence, collaboration, communication, composite applications (mash-ups), content management, portals, process automation… you get the picture.

This post charts the progress from SharePoint’s initial beginnings through to the end-to-end information management platform that it is becoming, and the market changes that have also occurred along the way. The attached diagram provides the visual version. It should be noted that what follows are my own thoughts and opinions, and they do not necessarily represent the views of any employers, past, present or future 🙂 It’s particularly relevant to this post, given I worked for Microsoft from 2000 – 2005 and at one point was the UK lead for SharePoint.

1997 – 1999

Before SharePoint arrived, there was a product called Site Server (and Site Server Commerce Edition) that contained features including: web content management and replication, site analytics, personalisation, indexing/search, document management and ecommerce. Site Server felt less like a product, more a collection of tools that didn’t have a home any where else. At the time, there weren’t too many servers to choose from. King of the range was Exchange Server (version 5.5), the messaging platform. SQL Server 6.5 was paddling around in the nursery pool.

In 1998 Microsoft announced that the next version of Exchange, codename Platinum, would include a new information store – the Web Store – designed for handling documents and web content, as well as email. A new product, codename Tahoe, would enhance Platinum by introducing document management through a technology called WebDAV – Document Authoring and Versioning – and an improved indexing/search engine. A separate project was also underway – developing the Local Web Store – to provide local replication of content between client and server. (If this all sounds familiar, you’ve probably worked with Lotus Notes…)

The combination of Platinum and Tahoe would be Microsoft’s next generation messaging, collaboration and document management platform. Of the remaining Site Server features, content replication moved into a new product called Application Center. Commerce Edition kept the personalisation, ecommerce and site analytics, and was renamed Commerce Server. The web content management features were, from memory, pretty ugly and retired to be replaced by a product acquisition…

In April 1999, a toolkit originally called the Digital Dashboard Starter Kit was released as a free download and introduced Microsoft’s first portal framework. The UI could sit in a browser or in Outlook and contained ‘nuggets’ displaying information from different content sources. Nuggets would later be renamed as web parts.

2000 – 2001

In 2000, Microsoft finally released Windows Server 2000 (upgrade from NT 4.0, introducing Active Directory) and SQL Server 2000 (upgrade to SQL Server 6.5). Exchange Server 2000 was completed and also released. All three releases were major product upgrades. Tahoe began the year in beta 1 development. The Digital Dashboard Starter Kit was up to its third release and renamed Digital Dashboard Resource Kit.

By mid-2000, the portal market was taking centre stage and, in October, Tahoe beta 2 was released complete with a new UI based on the Digital Dashboard Resource Kit. Tahoe had adopted a portal UI. It’s product name was finally announced – SharePoint Portal Server 2001 (SPS 2001).

By late-2000, SQL Server 2000 was outperforming its stable mate – Exchange 2000, and in December 2000, Microsoft (Steve Ballmer to be precise) killed the Local Web Store project, announcing that future database development would be based on SQL Server 2000.

Early in 2001, SPS 2001 was finally released. Having started life as a document management and indexing application, its new focus was on targeting the growing portal market. Whilst its features were basically good, it was saddled with two major problems – the web store and the digital dashboard. The web store underperformed, limiting the scale of the product. The digital dashboard was outside of Microsoft’s core development platform – Visual Studio – and had limited support within the developer community.

Also in 2001 Microsoft acquired content management vendor nCompass, and re-branded the product Content Management Server 2001 (CMS 2001). Initially the product was targeted with providing CMS capabilities for Commerce Server (re-completing the feature set that existed back in Site Server days). However, as the portal market continued to grow and overlap with the existing web content management market, CMS 2001 began to compete with SPS 2001.

And to further confuse customers, Microsoft also released a free add-on to Office 2000 called SharePoint Team Services (STS) that provided web-based team collaboration features. Confused? Plenty of customers were.

2002 – 2003

Development options for the next version of SharePoint were relatively simple – replace the Web Store with SQL Server as the storage back-end, and replace Digital Dasboard with ASP.NET for the front-end. As always, the devil was in the details – easy choices don’t necessarily lead to easy development. The focus was on improving scalability and improving portal features and that meant some of the document management features were going to struggle to be included. There’s a good reason why most document management systems choose to use a hierarchical database as opposed to a relational one for storing content… but that’ll have to wait for another blog post. As it was, features such as document profiles and workflow were left out of SPS v2. The relationship between SPS and STS needed sorting out, and the two groups were merged together. CMS continued on its own path, with an upgrade – CMS 2002 – that used ASP.NET as the front-end.

In October 2003, Microsoft released a new version of Office – Office 2003 – and included the new upgraded SharePoint range within the Office brand. STS was renamed Windows SharePoint Services (WSS), and became part of Windows Server 2003. It provided a collaboration store and a web part user interface built using ASP.NET. SPS v2 was built on top of WSS and named Microsoft Office SharePoint Portal Server 2003 (SPS 2003). SPS contained indexing/search, personalisation and enhanced management/taxonomy.

So we now had a portal product with a bit more scale than its predecessor that used Microsoft’s common developer tools (well, pretty much). Microsoft began to creep up Gartner’s magic quadrant for portals, and all would have been well if it hadn’t been for Enron and WorldCom…

2004 – 2006

Just as SharePoint moved away from document management and focused on portal capabilities, Sarbannes-Oxley was born and, all of a sudden, document and records management moved back up the agenda. Simultaneously, the continued growth of the portal market made it clear that portals and web content management were on a collision course, with document and records management joining the party.

CMS and SPS finally joined together as the two product groups were merged in 2004. Web parts built using ASP.NET were beginning to take on a life of their own and were moved fully into the developer playground. ASP.NET v2, launched at the end of 2005 includes native web parts. Workflow was back on the agenda, and now there is a common engine to build around – Windows Workflow Foundation (WinWF). Just like Windows SharePoint Services (WSS), WinWF will be a native add-on to Windows Server, providing a workflow service that all other applications can build upon.

Another missing piece of the SharePoint puzzle has been offline synchronisation. The local web store was originally going to be used, but that project was cancelled before it was ever launched. Outlook was the logical place to introduce such a feature and, sure enough, you will be able to have offline SharePoint folders in Outlook when the next version is released. But in 2005, Microsoft acquired Groove, a peer-to-peer (P2P) team-based collaboration product that also includes synchronisation of SharePoint sites. This will likely cause some confusion again with customers, similar to when STS and SPS first appeared. Adding to the confusion is the fact that Groove has its own built-in forms service, and InfoPath also provides a forms service.

Whilst compliance requirements have sobered up the content management party, business intelligence (BI) helps put back some fizz. Portals have always been the logical place for BI to come of age, moving away from the niche specialists such as business and data analysts to become integrated in every day work. In 2005, Microsoft released Business Scorecard Manager 2005 (BSM 2005), including integration with SharePoint. And in 2006, they acquired ProClarity. Alongside MOSS 2007 will be a a new product – Microsoft Performance Point 2007 – providing pervasive BI capabilities. Get ready to see some really badly designed dashboards 🙂 but that’s another post waiting to be written.

So, when version 3 of SharePoint is released (I’m guessing it will be some time in the first quarter of 2007, although the official estimate is still end of 2006), it will finally include the full set of capabilities first introduced in Site Server 10 years earlier, albeit in a far more grown up and usable format. It will also include quite a few additional features that have emerged since. I haven’t even touched upon the support for blogs, wikis and RSS, Excel services, Forms server or the new social networking capabilities provided by the Knowledge Network component, or the mash-up features that will enable composite applications, or related products such as Project Server. There is one area that does still contain duplication of features from the original Site Server. SharePoint has its own personalisation store and site analytics. So does Commerce Server. Will we see them join forces in the future?

That’s pretty much it for now. There’s a few other bits and pieces I’ve left out and I’ve tried not to include any non-public titbits around the development cycles. And if I went it to any more detail, I may as well start writing a book instead because this post is already a little on the long side. SharePoint has had an interesting journey, with curve balls thrown from all directions as the market place has evolved and adapted to changing demands. But it provides a great picture of how Microsoft develops products and is able to adapt them as the market changes. Love or hate the company, you can’t not admire the relentless perseverance to improve and deliver a successful product.

source: http://www.joiningdots.net/blog/2006/08/sharepoint-history.html

SHAREPOINT 2007 ASSEMBLY TYPES AND CORRESPONDING TYPE IDS

SharePoint 2007 Assembly Types and Corresponding Type Ids

Posting this for reference for folks upgrading SharePoint 2003/2007/2010/2013. Some of these Type Ids may show up as “Unknown Type” in a Missing server file or server configuration issues in a MOSS 2007 PreUpgradeCheck report or in a SharePoint 2010 upgrade log file. Having these IDs in a searchable format on the internet can be a easy quick reference.

 

Assembly Type Name Assembly Type Id
Microsoft.Office.Excel.WebUI.ExcelWebRenderer 5bcfa7e9-c525-2397-4f95-fe132713edc1
Microsoft.Office.Excel.WebUI.InternalEwr d783dcc4-91a6-18a9-9945-7d6f40960190
Microsoft.Office.Server.Search.WebControls.ActiveCrawls c54a0f4e-d855-ad45-ef85-4e67abf15a4d
Microsoft.Office.Server.Search.WebControls.AdvancedSearchBox ddbfb079-d77d-89c8-cb82-213960b44379
Microsoft.Office.Server.Search.WebControls.CompletedCrawls 6172b769-e922-1e5e-b706-1073173cbce3
Microsoft.Office.Server.Search.WebControls.CoreResultsWebPart f5c3ff60-e752-3a90-84f8-3677f8384e2d
Microsoft.Office.Server.Search.WebControls.FederatedResultsWebPart a70e5d2b-5a28-f448-159a-41473b653477
Microsoft.Office.Server.Search.WebControls.HighConfidenceWebPart fb35a198-aea0-3c26-e40c-df473fe9b07b
Microsoft.Office.Server.Search.WebControls.PeopleCoreResultsWebPart 8b764eff-2503-2180-42b0-b3f636741b21
Microsoft.Office.Server.Search.WebControls.SearchPagingWebPart f2c50a02-9894-4ace-bb3f-4146a24cd940
Microsoft.Office.Server.Search.WebControls.SearchStatsWebPart d55b3b6b-6281-707b-73d0-0c49581475ad
Microsoft.Office.Server.Search.WebControls.SearchSummaryWebPart 669602d9-e116-ccb8-eea3-e37ad589b14b
Microsoft.Office.Server.Search.WebControls.Subsystems 98ad0b1d-3e9e-338a-b595-48ef48ef023b
Microsoft.Office.Server.Search.WebControls.SystemStatus bc0158dd-a329-57ce-3563-1afacb17ec6c
Microsoft.Office.Server.Search.WebControls.TopFederatedResultsWebPart 87ddc87a-978c-58c9-6a9a-8bec4b97256d
Microsoft.SharePoint.Meetings.CustomToolPaneManager 270bad4c-2f8b-569a-2f06-ce4f80e608b0
Microsoft.SharePoint.Meetings.PageTabsWebPart 37f74547-a02f-044a-5ebc-823369a6f5da
Microsoft.SharePoint.Portal.WebControls.ApplyFiltersWebPart ff565657-a22e-f936-8645-968281b98e52
Microsoft.SharePoint.Portal.WebControls.Audience_List 7f14e4de-7f74-097c-f89c-4ee4752e2078
Microsoft.SharePoint.Portal.WebControls.BlogView 6c164bf5-4479-de30-bae2-8eac55218e4c
Microsoft.SharePoint.Portal.WebControls.BreadCrumbTrail 383b729c-bf1f-9bbc-c5ab-bc86244c1b69
Microsoft.SharePoint.Portal.WebControls.BrowseSites 72b44761-4232-af54-e158-daf1efe41483
Microsoft.SharePoint.Portal.WebControls.BusinessDataActionsWebPart fb61e73c-c113-5fb8-8117-8725e4d9df12
Microsoft.SharePoint.Portal.WebControls.BusinessDataAssociationWebPart 7a951d00-7bcc-9e8b-6d5e-67967be9326f
Microsoft.SharePoint.Portal.WebControls.BusinessDataDetailsWebPart f6bfd4dd-e6b5-7cb0-e080-e7674fcdd856
Microsoft.SharePoint.Portal.WebControls.BusinessDataFilterWebPart 55748b7b-bb94-24be-186a-14bbd49ce9c8
Microsoft.SharePoint.Portal.WebControls.BusinessDataItemBuilder 62465d8e-6e6c-107f-3c5e-ad1b897371f5
Microsoft.SharePoint.Portal.WebControls.BusinessDataListWebPart e73f6076-93d4-fc15-d5c5-3be3d0dbfda5
Microsoft.SharePoint.Portal.WebControls.CategoryDetail 1b7cebfb-6b67-179b-1dca-b934d976b5e2
Microsoft.SharePoint.Portal.WebControls.CategoryResultsWebPart b620591f-ce04-2efb-7b19-256f5fd94ca7
Microsoft.SharePoint.Portal.WebControls.CategoryWebPart f62babb5-a14d-11a7-ae1a-537c36fc53ae
Microsoft.SharePoint.Portal.WebControls.ContactFieldControl 74bd016c-baa0-14a8-d5d8-b75dc7e6f429
Microsoft.SharePoint.Portal.WebControls.ContactLinksMacroView 5b666014-c66a-3426-9d21-d41ae2786965
Microsoft.SharePoint.Portal.WebControls.ContactLinksMicroView 7e1c4e1d-c33b-7b72-b38d-9f9d2f2132e4
Microsoft.SharePoint.Portal.WebControls.ContactLinksPublicView 74956925-64c5-f51b-1b6d-6fbc37f3642d
Microsoft.SharePoint.Portal.WebControls.ContactLinksSuggestionsMicroView 389868b4-4dec-deae-a1eb-540826b89468
Microsoft.SharePoint.Portal.WebControls.ContactLinksWizardMicroView b3445824-a14b-c6e2-62d0-701c70a4e529
Microsoft.SharePoint.Portal.WebControls.DateFilterWebPart 2e6eb74e-daed-50ad-b6e2-b376543d2656
Microsoft.SharePoint.Portal.WebControls.GroupDetailWebPart 72511156-5087-513b-2a06-6b8f1d8373ca
Microsoft.SharePoint.Portal.WebControls.IndicatorWebpart 6bb48a6c-b412-b928-e325-136335a73a63
Microsoft.SharePoint.Portal.WebControls.InputFormContactLinksSuggestionsMicroView 5929bb44-edf6-fe9f-1a62-98d53f9d0c06
Microsoft.SharePoint.Portal.WebControls.InputFormMySiteWizardColleagueSuggestionsWebPart d5fbabb5-38fe-08d3-50e1-206148347e37
Microsoft.SharePoint.Portal.WebControls.IViewWebPart d332deb7-23b8-ea72-bbe9-734a248c1d17
Microsoft.SharePoint.Portal.WebControls.KPIListWebPart 8bc619d2-cd95-2e79-eae8-95302188e7fb
Microsoft.SharePoint.Portal.WebControls.ListingSummary 5fe113fa-f5b4-d2a0-77cc-59f1faed167b
Microsoft.SharePoint.Portal.WebControls.LogFilters dbffc15e-2d59-c124-b16b-2058d79d9173
Microsoft.SharePoint.Portal.WebControls.LogOverview e90bcdb1-48b3-cb0f-50e7-4bbd0631ea4f
Microsoft.SharePoint.Portal.WebControls.ManageDSServer dd8b1bda-72a2-0990-a795-f9153f4f2936
Microsoft.SharePoint.Portal.WebControls.ManagePrivacyPolicyControl c4baee83-b03a-c9e5-e14d-faed8a285f50
Microsoft.SharePoint.Portal.WebControls.ManageProfileProperty 4cbecc76-9f4f-2b5f-976b-efd3d941c415
Microsoft.SharePoint.Portal.WebControls.Member_List 5f689c4b-0407-dd9a-3063-223fa68a6fa8
Microsoft.SharePoint.Portal.WebControls.MembershipsMacroView ec6e27c1-390d-34cc-d940-c64ec21af4fe
Microsoft.SharePoint.Portal.WebControls.MembershipsMicroView a247d215-135c-30f8-f233-d43c2f66d2aa
Microsoft.SharePoint.Portal.WebControls.MembershipsWizardMicroView 57f9c7b4-a74f-78b6-1e63-b3f2ec59f548
Microsoft.SharePoint.Portal.WebControls.MembersWebPart 3d9a3a88-5341-fa01-9cd1-8459cc478571
Microsoft.SharePoint.Portal.WebControls.MySharedContext b6bffcc1-598e-9936-e8b1-35cd9578eb97
Microsoft.SharePoint.Portal.WebControls.MySiteGradualUpgradeRedirectionWebPart 6c9ff108-68c7-296f-82c4-8a585b86bbdd
Microsoft.SharePoint.Portal.WebControls.MySiteWizardColleagueSuggestionsWebPart f1475f55-53a0-6781-1f88-d58abc562300
Microsoft.SharePoint.Portal.WebControls.OWACalendarPart aff3123a-7408-8299-7972-0cede33641c7
Microsoft.SharePoint.Portal.WebControls.OWAContactsPart ff0d0027-04fb-741a-60e6-50f1ae4022d9
Microsoft.SharePoint.Portal.WebControls.OWAInboxPart be9d52a6-215a-802f-019b-c0aad99f8185
Microsoft.SharePoint.Portal.WebControls.OWAPart 7bca1c1d-472d-d5be-460b-9c4fed3132e9
Microsoft.SharePoint.Portal.WebControls.OWAPartBase a6a6861a-717a-3acf-4463-7f3755907453
Microsoft.SharePoint.Portal.WebControls.OWATasksPart 6a0ee437-7bd0-e3df-148e-93a38c919d9f
Microsoft.SharePoint.Portal.WebControls.PageContextFilterWebPart 7a26bc9e-b986-dca6-3955-363f098fb88b
Microsoft.SharePoint.Portal.WebControls.PeopleSearchBoxEx 20d975df-b490-24ae-578f-7202cd3bd804
Microsoft.SharePoint.Portal.WebControls.PersonalWelcomeWebPart 226014dd-d5b4-1546-0d96-356604d42978
Microsoft.SharePoint.Portal.WebControls.PortalQuickStartGuide e58d780c-cb4c-7981-989a-78a2e43bbcb8
Microsoft.SharePoint.Portal.WebControls.PrivacyItemViewer 90f74023-4fba-3192-87ad-16db9324d586
Microsoft.SharePoint.Portal.WebControls.ProfileDocuments 861a6d48-fa24-a769-b176-ad0dd247110e
Microsoft.SharePoint.Portal.WebControls.ProfileManages 1a17d6bc-9d17-189f-1271-30a4e47f6a24
Microsoft.SharePoint.Portal.WebControls.ProfileQueryPreferredName b6d2d30b-1c0c-acab-29fb-cfe803052a9a
Microsoft.SharePoint.Portal.WebControls.ProfileQueryUsers b0568e4e-b193-dcd4-47b8-d657b22a7af9
Microsoft.SharePoint.Portal.WebControls.QueryStringFilterWebPart aa8bfb6f-0281-35a0-46c8-b4af8458133e
Microsoft.SharePoint.Portal.WebControls.QuickLinksMacroView 68d6078f-da3d-2c8d-a1ae-934c0a95dc13
Microsoft.SharePoint.Portal.WebControls.QuickLinksMicroView 4f1b2104-b0b7-4513-08ec-39c4078764cc
Microsoft.SharePoint.Portal.WebControls.QuickLinksPublicView 7b1de259-773a-fcc9-4440-c616e54e4cf6
Microsoft.SharePoint.Portal.WebControls.RelatedGroupsWebPart 66343a52-ab7c-b90c-5574-291e75d9bdbc
Microsoft.SharePoint.Portal.WebControls.ReportMetadataStrip 191c8554-9ba9-7c49-adbb-996ec6213518
Microsoft.SharePoint.Portal.WebControls.RightBodySectionSearchBox 92388a33-0e0a-9d09-2b91-1f07c9e1093e
Microsoft.SharePoint.Portal.WebControls.RSSAggregatorWebPart bc877bd0-b48e-3165-7c9e-1e2f98c2a42a
Microsoft.SharePoint.Portal.WebControls.ScopesList c18f19e1-3c25-db9a-bdd9-a6181d9c010e
Microsoft.SharePoint.Portal.WebControls.ScorecardFilterWebPart 06bf9699-37c1-bedd-e1b0-c50a5ea15da5
Microsoft.SharePoint.Portal.WebControls.SearchBox be3f4229-565c-e537-0e14-88122f3ee5c3
Microsoft.SharePoint.Portal.WebControls.SearchBoxEx f5897322-ddd4-c990-d012-f9d4fe2180ad
Microsoft.SharePoint.Portal.WebControls.SearchResults 58d12259-07ae-6f52-9559-96299aad5135
Microsoft.SharePoint.Portal.WebControls.SharedWorkspaces 8cc36d38-feb4-eea2-1467-e6bcb489dd1f
Microsoft.SharePoint.Portal.WebControls.SingleSignonApplicationList 3b96eacc-eed7-2b9c-1c28-f2b654187dab
Microsoft.SharePoint.Portal.WebControls.SiteDocuments ac9e7c86-6477-9737-1dc1-c84b7906cf0c
Microsoft.SharePoint.Portal.WebControls.SpecialTermsList ac03acc8-a417-b56c-2ba5-aa6f229cd345
Microsoft.SharePoint.Portal.WebControls.SpListFilterWebPart e265a361-507e-136e-ceb3-20d04a556a22
Microsoft.SharePoint.Portal.WebControls.SPSlicerChoicesWebPart 33df9f5d-8911-b19c-11fd-943857f07263
Microsoft.SharePoint.Portal.WebControls.SPSlicerTextWebPart 45ee4378-96e2-349b-00a6-89312cde5ccf
Microsoft.SharePoint.Portal.WebControls.STSQueryParts c7729637-18d2-72d0-cb81-4d900765c532
Microsoft.SharePoint.Portal.WebControls.TasksAndToolsWebPart cf30d33b-5ccd-3923-9dee-e3c9f31851c9
Microsoft.SharePoint.Portal.WebControls.ThisWeekInPicturesWebPart a2e08067-888b-2ca1-4b3d-2bb33bdc3b37
Microsoft.SharePoint.Portal.WebControls.TOCPart 8404b510-5dbc-8c34-b448-51632893010a
Microsoft.SharePoint.Portal.WebControls.UserContextFilterWebPart f3893ef4-c63c-e621-92b8-4ccc4d24ac00
Microsoft.SharePoint.Portal.WebControls.WebPartLoc 7c0b28b8-6250-a8e2-7ad0-1eb2bf83cbf1
Microsoft.SharePoint.Portal.WebControls.WSRPConsumerWebPart 2a79f135-fb74-275e-733b-ebc0d3a05813
Microsoft.SharePoint.Publishing.WebControls.ContentByQueryWebPart 2f1510c7-75d5-921f-b120-2ce98fe3afe3
Microsoft.SharePoint.Publishing.WebControls.SummaryLinkWebPart db128878-9a93-4768-2256-cc2c390ffb57
Microsoft.SharePoint.Publishing.WebControls.TableOfContentsWebPart 9f030319-fa14-b625-4892-89f6f9f9d58b
Microsoft.SharePoint.Search.Internal.WebControls.CoreResultsWebPart f9012503-2862-2cae-4196-0334f3908737
Microsoft.SharePoint.Search.Internal.WebControls.SearchPagingWebPart 95e9deb3-b312-4574-7cc8-8f9d8fb00d3d
Microsoft.SharePoint.Search.Internal.WebControls.SearchStatsWebPart 8fe9d300-7633-44c7-b078-c59bed6ef7ce
Microsoft.SharePoint.Search.Internal.WebControls.SearchSummaryWebPart 84af9101-7f3b-83b1-61c7-639dd9ed809a
Microsoft.SharePoint.WebControls.TopologyViewWebPart 08f1dc7f-a471-2beb-1e5b-00ea35abba18
Microsoft.SharePoint.WebPartPages.BlogAdminWebPart 99cdf365-0cee-2fb2-c12b-ce285a898031
Microsoft.SharePoint.WebPartPages.ChartViewWebPart d5850dc1-f809-9504-e796-e5461dde4b39
Microsoft.SharePoint.WebPartPages.ContentEditorWebPart e60f6c95-e86c-4717-2c0d-6d8563c9caf7
Microsoft.SharePoint.WebPartPages.DataFormWebPart b9a7f972-708a-cd77-4ffd-a235dfed5c38
Microsoft.SharePoint.WebPartPages.DataViewWebPart b4189111-1798-c9a4-3f0a-5a70c619f9cc
Microsoft.SharePoint.WebPartPages.ImageWebPart ce9aa113-48cf-ddee-0c03-597445e5b7ab
Microsoft.SharePoint.WebPartPages.ListFormWebPart 293e8d0e-486f-e21e-40e3-75bfb77202de
Microsoft.SharePoint.WebPartPages.ListViewWebPart 2242cce6-491a-657a-c8ee-b10a2a993eda
Microsoft.SharePoint.WebPartPages.MembersWebPart d839800d-03b8-abd7-55f8-b6930f0b5abe
Microsoft.SharePoint.WebPartPages.PageViewerWebPart 34775302-228e-4263-e421-a175e9ebeb06
Microsoft.SharePoint.WebPartPages.SimpleFormWebPart 404822d6-cc74-7e5c-6767-b8206c1490fc
Microsoft.SharePoint.WebPartPages.TitleBarWebPart 94e9c166-264a-f84b-2377-bccefb8b3771
Microsoft.SharePoint.WebPartPages.UserDocsWebPart c17f9896-5c01-bf29-48af-096fd218184e
Microsoft.SharePoint.WebPartPages.UserTasksWebPart f94b483e-dc6e-f8a2-2867-10bd9897f35f
Microsoft.SharePoint.WebPartPages.XmlWebPart c4903013-30d3-53d1-b39a-30a756e83e37

the 14 hive

If you are familiar with SharePoint 2007, you must be aware of the “12 hive” directory. In SharePoint 2010, the “12 hive” directory has been replaced by “14 hive” directory. In most cases this is the default path for SharePoint files.

Following are some of the folders in the “14 hive” directory:

  1. Program Files\Common files\Microsoft Shared\Web Server Extensions\14 – This directory is the installation directory for core SharePoint Server files.
  2. Program Files\Common files\Microsoft Shared\Web Server Extensions\14\ADMISAPI – This directory contains the SOAP services for Central Administration. If this directory is altered, remote site creation and other methods exposed in the service will not function correctly.
  3. Program Files\Common files\Microsoft Shared\Web Server Extensions\14\CONFIG – This directory contains files used to extend IIS Web sites with SharePoint Server. If this directory or its contents are altered, Web application provisioning will not function correctly.
  4. Program Files\Common files\Microsoft Shared\Web Server Extensions\14\LOGS – This directory contains setup and run-time tracing logs.

Following are some new folders added in the “14 hive” directory:

  1. Program Files\Common files\Microsoft Shared\Web Server Extensions\Policy
  2. Program Files\Common files\Microsoft Shared\Web Server Extensions\UserCode – This directory contains files used to support your sandboxed solutions.
  3. Program Files\Common files\Microsoft Shared\Web Server Extensions\WebClients – This directory contains files related to the new Client Object Model.
  4. Program Files\Common files\Microsoft Shared\Web Server Extensions\WebServices – This directory contains new WCF or .svc related files.

Thanks to Viralshah23

Product Manager
India India
%d bloggers like this: