Today is the last chance to register for the BIWUG session about SharePoint 2010 – with 90 people registered there are only 10 seats available….
PS I will do the Introduction to SharePoint 2010 …
Occasional rantings about Dynamics CRM/365, Power BI and Azure cloud. Taking the first small steps in machine learning, Python and algorithmic trading
Today is the last chance to register for the BIWUG session about SharePoint 2010 – with 90 people registered there are only 10 seats available….
PS I will do the Introduction to SharePoint 2010 …
I noticed that when I tried to open the SharePoint 2010 Management Shell on my machine I got an error stating:
Exception setting "ThreadOptions": "This property cannot be changed after the Runspace has been opened." At C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\CONFIG\POWERSHELL\Registration\SharePoint.ps1:2 char:48
+ if ($ver.Version.Major -gt 1) {$Host.Runspace. <<<< ThreadOptions = "ReuseThread"} + CategoryInfo : InvalidOperation: (:) [], RuntimeException + FullyQualifiedErrorId : PropertyAssignmentException
Thanks to Bill Baer for providing me with a solution in the SharePoint 2010 forums –installing Update KB968930 which contains the Windows Management Framework Core package fixed the error.
The SharePoint 2010 Client Object Model feature is definitely in my top 10 list of SharePoint developer enhancements. It basically provides an abstraction layer so that client apps can interact with SharePoint – there are basically 3 flavors of Client Object Models:
These 3 client models all talk with SharePoint through the client.svc WCF service and all provide complete access to SharePoint artifacts such as site collections, sites, lists, items, files, folders, webparts, security, content types, etc …
If you need to retrieve data you will typically have 3 steps you need to perform:
There is a great series of blog postings from Steve Peschka about practical use of the Client OM:
This is something which will probably bite you in the **s, when you start developing against SharePoint 2010. Don't forget to change the “Platform target” to x64 or AnyCPU
SharePoint 2010 only support 64-bit OS so your apps should do the same. So if you don't change it you will see some strange errors – even something as simple as creating a new SPSite object will throw an error stating:
"The Web application at http://intranet.contoso.com could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application."
So the error message is not very helpfull in this case ...I’m using VS2010 Beta2 on Windows Server 2008 R2 within VMWare Workstation and noticed that some parts of Visual Studio were not rendering or rendered in the wrong location – see for example the “New project dialog” which seemed to be missing some stuff.
This KB provided the solution for these issues – Disable SVGA drivers installed with VMWare Tools on Windows 7 and Windows 2008 R2…
I finished installing my new SharePoint Server 2010 Dev box a couple of weeks ago … and forgot to publish this post. So here it goes. Installing a SharePoint Server 2010 is not that difficult since there is a lot of guidance out there. It’s really amazing how detailed the documentation is – especially since we are only at Beta 2. So what documentation did I use:
So here’s my software configuration:
All the above prerequisites are the same for SharePoint Server 2010 and SharePoint Foundation 2010 (except for the ADOMD.NET which is used for Excel Services and PerformancePoint Services – thanks Spence for the clarification). So if you plan to create both – this is the moment to create a snapshot. Next just follow the steps as outlined in Deploy a single server with SQL Server (SharePoint 2010)
On to the installation of language packs – I definitely want to check out the new MUI experience. For documentation take a look at Deploy language packs (SharePoint Server 2010) – same applies as for SharePoint Server 2007 - you must first install the SharePoint Foundation 2010 language packs before you install the SharePoint Server 2010 language packs. However I did not see the step with “On the Modify Server Farm Settings page, click Do not disconnect from this server farm, and then click Next.”
Afterwards I installed Visual Studio 2010 beta 2 as well as the Visual Studio 2010 SDK – this is something which you should probably install before installing SharePoint because the first time everything froze during install and I had to restart.
PS I’m using a Dell Precision M4400 with 8 GB RAM and SSD hard disk to run this stuff … works like a charm.
The Developer Dashboard is a great feature for developers in SharePoint 2010 which enables us to troubleshoot and debug SharePoint pages – take a look at Using the Developer Dashboard in SharePoint 2010 for some great info.
So you can activate the Developer Dashboard in 3 ways:
$snapin = Get-PSSnapin | Where-Object {$_.Name -eq 'Microsoft.SharePoint.Powershell'}
if ($snapin -eq $null)
{
Write-Host "Loading Microsoft SharePoint Powershell Snapin"
Add-PSSnapin "Microsoft.SharePoint.Powershell"
}
$dash = [Microsoft.SharePoint.Administration.SPWebService]::ContentService.DeveloperDashboardSettings;
$dash.DisplayLevel = 'OnDemand';
$dash.TraceEnabled = $true;
$dash.Update()
SPWebService.ContentService.DeveloperDashboardSettings.DisplayLevel = SPDeveloperDashboardLevel.Off;
SPWebService.ContentService.DeveloperDashboardSettings.Update();
It is considered best practice to create a central document library with all of the document templates you are using in your different SharePoint content types in SharePoint Server 2007. This way you can easily update your document template without the need to redeploy or change your SharePoint content type. Unfortunately this caused problems with Office which did not seem to be able to find the centrally located template. Fortunately installing Office 2003 Service Pack 3 fixed the problem.
I just converted a Hyper-V image back to a VMDK to use it in VMWare Workstation using StarWind V2V Convertor. Works like a charm and it is free …
I will be teaching the SharePoint 2010 Partner Ignite training for Developers from December 14th to December 16th. Topics I will be covering:
• SharePoint 2010 Developer Roadmap
• SharePoint Development with Visual Studio 10
• SharePoint UI Advancements
• Designing Lists and Schemas
• LINQ to SharePoint
• Client Object Model
• SharePoint 2010 Workflow
• The SharePoint 2010 Services Architecture
• External Data in SharePoint (BCS)
• Enterprise Content Management (ECM)
• Extending Search
• BI Solutions
This is a Classroom Training session for Microsoft Partners. You can subscribe for this event if you are as an individual associated to a Company registered in the Microsoft Partner Program. Go to the Phttps://training.partner.microsoft.com/learning/app/management/LMS_ActDetails.aspx?UserMode=0&ActivityId=559841artner Learning Center to register
BIWUG is back with our first session about SharePoint 2010. Our next session is the 17th of december in the new Ordina offices in Mechelen. We have a great line up amongst which 3 Belgian SharePoint MVPs presenting. Here’s the agenda:
Please register on the BIWUG site.