Tip Of DAY

Tip1: For optimal performance, the current best practice is to keep all your

service applications in one application pool. This may change as the product

evolves, but it makes the most sense for now. Application pools consume a great

deal of resources, and performance testing has shown that you get the best results

when all your service applications are in one application pool.

Tip 2: A custom service application proxy group created for one web application cannot be associated with other web applications

Tip 3: How SharePoint getting domain user details before user profile synchronization

The "People Picker" control will directly query the domain users from Active Directory in SharePoint 2010, it doesn't query the user information from User Profile service application, so it can resolve the users without User Profile service application.

Tip 4: After the release of .NET Framework 4.0, the GAC (global assembly cache) was split into two– one for .NET 1.0 through 3.5 (“c:\windows\assembly”) and

– other for .NET Framework 4.0 (“c:\windows\microsoft.net\assembly”).
So for any SharePoint projects created in Visual Studio 2012 (with .net 4.0), by default, all the dlls are deployed to c:\windows\microsoft.net\assembly path and not the earlier GAC path.

Tip 5: When you try to modify a SharePoint 2013 Master Page, you edit master page’s .html only. The associated master page file gets updated automatically.
So don’t attempt to modify only the .master as it should be perfectly in sync with it’s html counterpart.