Visual Studio 2010 Console Application for SharePoint 2010 (Target Platform + .NET Framework)

Most of the time it is very handy to test out something using
console application against SharePoint 2010. But this could be painful for at
times as developers finds it that references does not pick the assembly
correctly/build fails

Here are two things that you need to be careful of when
developing something on console application.

1. The target platform of your console application
needs to be set as x64(64 bit) in the Build configuration of your project.

2. The target framework needs to be .NET 3.5

As soon as setting up the User Profile Synchronization Application service, when clicking on User Profile Service Application in SharePoint 2010 - UserProfileServiceUserStatisticsWebPart:LoadControl failed

As soon as setting up the User Profile Synchronization Application service, when clicking on User Profile Service Application in SharePoint 2010 - UserProfileServiceUserStatisticsWebPart:LoadControl failed

[UserProfileServiceUserStatisticsWebPart:LoadControl failed, Exception: System.IO.FileLoadException: The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.InitializeIlmClient(String ILMMachineName, Int32 FIMWebClientTimeOut) at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager..ctor(UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID)]
Check-1: You may have forgotten to issue iisreset /noforce
Check-2: Verify that “Forefront Identity Manager Synchronization Service” and the “Forefront Identity Manager Service” are running

SPSite Constructor throws FileNotFoundException

Most of the time we try out a Console application to test a specific piece of code, but when you do this on a x64 bit platform there is a chance that you might come across an exception as “FileNotFoundException” – complaining that the site not found.
The most basic reason for this issue could be that your output assembly is not compatible with the SharePoint assembly which is running out.
Ensure that your target platform is set to “AnyCPU”, before you further investigate on any other reasons.

Issues when running SharePoint 2010 Products Configuration Wizard - System.Security.Cryptography.CryptographicException: Keyset does not exist

Here the encryption key was created on a specific thread which was impersonated under a specific users account. When the .NET Finalizer processes the encryption key while the timer service shuts down it executed on a different thread which is not impersonated - so the key does not exist and you get an exception like "keyset does not exist".
To configure the server to no longer show a dialog when an unhandled exception occurs, use the registry editor to delete the following registry keys:

- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\DbgManagedDebugger
On a 64-bit operating system also delete the following registry keys:

- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug\Debugger
- HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\DbgManagedDebugger

iisapp equivalent in IIS7 (Related to Windows 2008 or above)

When working with IIS 6.0 it was pretty handy to use the iisapp VbScript to find out which w3wp worker process relates to which Application Pool. In IIS7, this script doesn’t work anymore. There is a replacement though. You can add the command below to a batch file and just call it:

%windir%\system32\inetsrv\appcmd.exe list wp

How to migrate your WSS 3.0 & MOSS 2007 (32-bit) Products to SharePoint 2010

The paths depicted below could help migrate your WSS 3.0 & MOSS 2007 (32-bit) Products to SharePoint 2010.
Products are needed to be migrated in their respective 64-bit versions and then their 64-bit versions will be Migrated to SharePoint 2010 which doesn’t offer any 32-bit support.
E.g. If you want to upgrade from 32-bit version of MOSS 2007 then firstly you need to upgrade to the 64-bit version of MOSS 2007 and then from 64-bit version of MOSS 2007 you can upgrade to SharePoint Server 2010.