Together with 3 colleagues from QNH Business Integration I am currently finishing implementing a already NEN 2082 certified project based on SharePoint 2010.
When SharePoint 2010 hits RTM there will be another audit for this version of SharePoint, because currently the pre release version has been certified.

NEN 2082 is a Dutch standard which is similar the DoD5015 and MoReq standards.

This project was done for the Gemeente Nieuwegein, which is a Dutch local Government.

For this project we have also been nominated for the “Innovation of the year” award:

More information (Dutch)

My colleagues at QNH:

• Jeffrey Tummers - http://blog.thumnet.com
• Alexander Ketelaar – http://sharepoint2010.nl
• Robert Sep

Last week, I removed my VS2010 beta installation and installed VS2010 RC. The RC is much more stable, and as a bonus renaming a feature in a SP2010 project now works.
We have been building lots of features lately, and I was very pleasantly surprised to see this bug already fixed.

A collegue created a SP2010 workflow in visio, and imported it into SharePoint Designer 2010.
His flow used the following actions: 

• AddListItemPermission
• InheritListItemPermissions
• RemoveListitemPermission
• ReplaceListItemPermissions

SharePoint Designer 2010 throws an error when he validates the workflow (check for errors) or tried to deploy it.

The error (for searchablility):
This workflow action is not supported in this region of the workflow.
It can only be inserted in certain types of blocks.

SharePoint Designer does not show the actions as available.
After a bit of searching we found that these actions can only be added when inserted in an Impersonation Step.
This is logical as the impersonation step runs as the author of the document, in stead of the workflow starter.

Hope this is helpful.

Implemented AkismetExtension on the blog a week ago, and it seems to be working.

Lets hope it lasts.

Alexander Ketelaar (www.sharepoint2010.nl) found the following list of known SP2010 beta 2 issues.

http://officebeta.microsoft.com/en-us/sharepoint-server-help/microsoft-office-servers-beta-2-known-issuesreadme-HA101267292.aspx?CTT=1

Thanks to Jeffrey Tummers for retrieving the id's

This tool makes contenttype development a lot easier.

Click the contenttype together in MOSS and copy the xml from this tool into your sharepoint solution.

This tool works with SP2010 beta.

http://www.codeplex.com/MOSS2K7CTypesViewer

A really nice (and funny) article why you should not do this, by Tyler Holmes.

http://blog.tylerholmes.com/2008/10/don-set-your-sharepoint-app-to-full.html

I came across this article because we had an assembly containing a feature reciever that would cause an error when executed.
Assemblies containing feature recievers should always go in the GAC (by design), but we where creating a custom policy.

So, I agree with Tyler that custum policies are still preferable, but when you have a dll that contains a feature reciever, you should just put it in the GAC.

Free download of Powerpoint slides, demos, video's and example code of around 40 .net courses.

http://dotnet-u.com/Courses.aspx

Enjoy.

DamienG, just posted a LINQ to SQL cheatsheet for C# and VB.net.

Download it at: http://damieng.com/blog/2009/08/12/linq-to-sql-cheat-sheet