
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.
9ec0c185-6803-4a62-9790-44df71fb014c|0|.0
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
6dd9a6be-04d4-4544-bb63-b13417ab91a2|0|.0
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.
6e851060-da62-4fb4-a897-5c2ef867ddb0|0|.0

Today I came across a iPhone app that enables you to browse SharePoint from your iPhone.
Haven't tried it myself because I use a windows mobile phone, but might be usefull for all you out there.
http://www.spyk.com/Products/iShare/Pages/iShare.aspx
Just thought I'd share...
12983c14-6f23-4078-93a7-417e180692fe|0|.0