We had:

<mapping Key="pdf" Value="icpdf.gif"/>

It should have been:

<Mapping Key="pdf" Value="icpdf.gif"/>

Quite an inconsistency in a single product!

BAD CODE (will apply only 1 mod):

SPFarm.Local.Services.GetValue().ApplyWebConfigModifications();
webApplication.Update();

GOOD CODE (will apply all mods):

webApplication.Update();
SPFarm.Local.Services.GetValue().ApplyWebConfigModifications();

So the punchline is that the sequence of the method calling does matter!

What do you need to do:

1. Point a MX (mail relay) DNS record to the SharePoint server. For example wss.company.com. This is because all email will have to be delivered to the SharePoint server.
2. Enable SMTP on your server http://www.itsolutionskb.com/2008/11/installing-and-configuring-windows-server-2008-smtp-server/
   
   
3. Configure incoming email on the SharePoint server with the following settings:
   

This should make it work. However when I tried it my drop folder kept getting cleaned (by the timer job) but the mail never appeared in the list. I played around with some settings and found these working:

• Hotkey Features Integration for Windows 7 (32-bit, 64-bit), Vista (32-bit, 64-bit), XP (32-bit, 64-bit) and 2000 - ThinkPad
• Fingerprint Software 5.9.3 for Windows 7 (64-bit) - ThinkPad, ThinkCentre, ThinkStation
• Intel AMT 6.0 - Management Engine Interface and Serial Over LAN driver (SOL) Driver for Windows 7 (32-bit, 64-bit), Vista (32-bit, 64-bit), XP - ThinkPad
• Conexant Audio Software for Windows 7, Vista and XP - ThinkPad T410, T410i, T410s, T410si, T510, T510i, W510, W701, W701ds, X201, X201i, X201s, X201 Tablet
• Intel Wireless LAN (bg, abg, abgn) for Windows 7 - ThinkPad
• Ricoh Multi Card Reader Driver for Windows 7, Vista - ThinkPad T400s, T410, T410i, T410s, T410si, T510, T510i, W510, W701 and W701ds
• NVIDIA Display Driver for Windows 7 64-bit - ThinkPad T410, T410i, T510, T510i, W510, W701, W701ds
• Intel Rapid Storage Technology Driver Windows 7 (64-bit), Vista (64-bit) and XP (64-bit) - ThinkPad T410, T510, W510, W701, W701ds, X201, X201i, X201s, X201 Tablet
• UltraNav driver for Windows 7 (64-bit), Vista (64-bit) and XP (64-bit) - ThinkPad
• USB 3.0 Driver for Windows 7, Vista and XP - ThinkPad W510, W701, W701ds
• Power Manager for Windows 7 and Vista - ThinkPad
• ThinkPad Power Management driver for Windows 7, Vista, XP, 2000, ME, 98 SE - ThinkPad

Installation instructions can be found here: http://blogs.technet.com/b/keithcombs/archive/2010/02/10/install-windows-server-2008-r2-on-a-lenovo-thinkpad-w510.aspx

The only think I didn't get to work is Bluetooth although there is something about it on http://www.tipandtrick.net/2008/how-to-enable-bluetooth-in-windows-server-2008-64bit-standard-edition/

To use my W510 with Win 2008 as desktop replacement I configured it this way:

FEATURES:

• .NET Framework 3.5.1 features
• Desktop Experience
• Wireless LAN Service
• Windows Biometric Framework

ROLES:

• Hyper V

Don't forget to:

• Turn off IE Enhanced Security Configuration and the Shutdown Reason dialog!
• Enable Wireless Zero Config service
• Start Audio Service and set startup to Automatic

var pc = new PrincipalContext(ContextType.ApplicationDirectory, "adserver:50000", "o=org,c=nl", ContextOptions.Negotiate, @"domain\user", "password");

Console.WriteLine("Connected to: {0}", pc.ConnectedServer);

var validUser = pc.ValidateCredentials("userToValidate", "passwordToValidate", ContextOptions.SimpleBind);

Console.WriteLine(validUser);

Note that the useraccount MUST be enabled (msDS-UserAccountDisabled = FALSE) and that userPrincipalName should be CN value. Otherwise the validatecredentials method always will return false.

SPFarm.Local.Solution["demo.wsp"].DeployedWebApplications;

Strange as I'm not even using a GUID in my code here. So a little breaking down led me to the conclusion that if you call the DeployedWebApplications property on a solution that is globally deployed you get this error.

A few months ago I figured out how to build STSDEV projects with Team Foundation Server. So here is the result step-by-step (only the steps that differ from the default project steps):

Adjust the target of the solution to DebugBuild. If you are only building STSDEV projects you can do this at once by changing following lines in TFSBuild.proj file:

<configurationtobuild include="Debug|Any CPU"></configurationtobuild>

to:

<configurationtobuild include="DebugBuild|Any CPU"></configurationtobuild>

or per solution:

<solutiontobuild include="$(BuildProjectFolderPath)/../../ExampleSolution.sln"></solutiontobuild><targets></targets><properties>Configuration=DebugBuild;Platform=Any CPU</properties></solutiontobuild>

Change the DebugBuild in the Microsoft.SharePoint.targets file and make it like this:

<pre name="code" class="xml"><target name="DebugBuild">

<copy condition="'$(IsDesktopBuild)'=='false'" destinationfolder="$(SolutionDir)bin\debug" sourcefiles="$(OutDir)$(TargetName).dll"></copy>

...

<copy condition="'$(IsDesktopBuild)'=='false'" destinationfolder="$(OutDir)" sourcefiles="$(SolutionDir)DeploymentFiles\$(PackageName)"></copy>

</target>

Override path to STSDEV for the build on the server (TFSBuild.proj):

<custompropertiesforbuild>STSDEV="C:\Software\STSDev v1.3\stsdev.exe"</custompropertiesforbuild>

Once this is done you can build your STSDEV projects on the TeamBuild server. Have fun!