Using SPContext.Current is no guarantee for great performance

It is a common best practice, while working with the SharePoint server API, to always use context objects whenever possible. Because they have been already instantiated by SharePoint itself, reusing context data doesn’t cause additional calls to the database and allows you to create good performing solutions. However, just because you use SPContext.Current in your code, doesn’t mean your solution is built properly.

Mavention SharePoint 2010 Site Checker Windows Phone 7 app available now

Recently, here at Mavention, we published Mavention SharePoint 2010 Site Checker – a set of automated tests that allows you to scan your Internet facing website built on the Microsoft SharePoint 2010 platform for common issues. Just now Mavention SharePoint 2010 Site Checker has become available as a Windows Phone 7 app.

Easier maintaining Web Parts with Visual Studio 2010 SharePoint Developer Tools

Visual Studio 2010 SharePoint Developer Tools simplify working with SharePoint 2010 projects. By introducing SharePoint Project Items (SPIs) the tools hide the internals of creating SharePoint packages and allow you to focus on the real work. However, when you start moving SPIs around, things might get complicated and break. Find out how to prevent yourself from spending hours on fixing stuff using the standard functionality of the new developer tools.

Easy inserting symbols in SharePoint 2010 with Mavention Insert Symbol

When working with content there are often situations when you need to insert a symbol such as a copyright or a trademark sign in content. If you are editing content directly in SharePoint there is no easy way for you to insert such symbol. You have to copy the symbol from another place and paste it in SharePoint. If this scenario sounds familiar to you, then the Mavention Insert Symbol solution is just the right thing for you. Find out how to insert symbols in content in SharePoint 2010 the easy way with Mavention Insert Symbol.