If you are running your own SharePoint infrastructure, you should take a look at a Security Advisory: http://www.microsoft.com/technet/security/advisory/983438.mspx
Microsoft is investigating new public reports of a possible vulnerability in Microsoft Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007. The vulnerability could allow an attacker to run arbitrary script that could result in elevation of privilege within the SharePoint site, as opposed to elevation of privilege within the workstation or server environment.
SP 2010 does not bring a SiteDirectory template. Microsoft Consulting Services UK have released a CodePlex version of a SiteDirectory for SharePoint 2010: http://spsitedirectory2010.codeplex.com/
What is the Purpose of the Site Directory for SharePoint 2010? SharePoint 2007 used to have a type of Site Called Site Directory which provided a directory of all sites that had been created. In SharePoint 2010, this feature has been dropped. This solution has been developed to fill the gap in SharePoint 2010.
Now you will think “Why not?”. Some time ago I read a blog post which said “If you are asking yourself if you want to install Office 2010 as 64bit version, you should install the x86 version”. Why that?
The reason is, that if you are asking yourself you worry about incompatibility with over software. And you are right! If you install x64, all add-ins you use have to be x64 as well.
SharePoint and Office are now available via MSDN subscription:
http://msdn.microsoft.com/en-US/subscriptions/subscription-downloads.rss
Update:
Microsoft SharePoint Foundation 2010 (English)
Microsoft SharePoint Designer 2010 (32-bit)
Microsoft SharePoint Designer 2010 (64-bit)
As you can read on the SharePoint Team Blog, SharePoint 2010 has reached RTM status.
There is word about availability on MSDN.
Our Volume License customers with active Software Assurance (SA) on these products will be one of the first to receive the 2010 set of products. They will be able to download the product in English, French, Spanish, German, Russian, and Dutch via the Volume Licensing Service Center starting April 27.
A quick test shows that the just released Visual Studio 2010 works on my SP 2010 Beta 2 VM.
I could open a project, hit F5 to deploy it and debug successfully.
What is a large list? What might be the problem if I store 1 million documents in a document library? Is there an improvement from WSS 3 to SharePoint Foundation?
If you want answers to the questions, take a look at a great post at the “Microsoft Enterprise Content Management (ECM) Team Blog”.
A summary to the problem:
Any time you ask for content from SharePoint, you have to specify how it’s sorted – for example, the All Documents view in SharePoint 2007 asks for the top 100 results, sorted by filename.
Am 13. April werden wir uns wieder um 18h in Paderborn treffen. (Net at Work Netzwerksysteme GmbH, Am Hoppenhof 32, Anfahrtsbeschreibung).
Als Thema ist ein Erfahrungsbereicht über die Migration von Lotus Domino/Notes nach SharePoint 2007 hören. Vielen Dank schon einmal an Campus Consult.
Wir bitten um eine kurze Anmeldung per Email an ug-owl ( at ) mysharepoint ( . ) de.
Am 12. Mai ist SharePoint 2010 release Termin. Zum weltweiten Launch der neuen SharePoint-Suite hat sich die SharePointCommunity etwas Besonderes überlegt.
A Webpart receives a filter value through the IWebPartField interface. The example over at MSDN was simple and clean. So I adopted the code to my Webpart.
A common scenario would be to create controls based on the received filter value. E.g. query a list for the passed filter value, and display the item from the query.
Problem
From the ASP.NET Lifecycle we know how to deal with controls. Create them in CreateChildControls, assign values in OnPreRender and let them being rendered in RenderContents.
Solutions which were developed for SharePoint Services V3 will most likely continue to work if you use them in a SharePoint Foundation environment.
But how do you find out which version your are dealing with? This is a question which might be important if you use V3 CSS elements which are not available under SharePoint Foundation.
The SharePoint version can be found from from the SPFarm.Local.BuildVersion property. For SharePoint V3 you’ll need permissions to access the configuration database to read the local farm.
