This is a useful article when converting a custom workflow project from Visual Studio 2008 to Visual Studio 2010: http://blogs.msdn.com/b/bethmassi/archive/2010/01/15/migrating-a-2007-workflow-to-visual-studio-sharepoint-2010.aspx In a nutshell, Go ahead with the conversion wizard Add a new Project (2010 Sequential Workflow Project) to the solution Rename the Workflow1  folder to the new name - Very Important, you have to keep this folder in order for the workflow to be in the feature, so just rename it. Copy the old workflow.cs file to the new folder in the new project. This will bring over the designer file and rules file (if applicable). Delete the worflow1.cs and update the class name to the new class name Copy over all other files that are not related to packaging such as Utility classes. Copy default namespaces to new project. Check your default namespaces, namespaces in Elements.xml, assembly versions Update namespace in new project on the .cs file, and .designer.cs file. [...]

Debugging Custom Event Receivers. Here's a weird error that took some time to figure out. Generic "Object reference not set to an instance of an object." Error on a custom SharePoint 2010 event receiver. If I went through the UI to change a field on a list, the event receiver fires fine. But, if a workflow changed the field it threw the error below. I finally found if I attached the OWSTimer process to Visual Studio, it would debug, but still not show the exact problem. The solution is to find the Log On account for OWSTimer in the Services console (services.msc) and then to grant that account permissions on the list that the event receiver is running on. Edit -checking the permissions of the OWSTimer account is just one possible solution.  What I found out was that the list was hanging on to old event receivers as well.  I [...]

We used this to delete users from the site collection in SharePoint 2007. It was gone in 2010, but really just "hidden." Simply paste the following URL into your browser and change the site name and you wll get the All People page back.  Useful for deleting users from the site collection. http://My2010Site/_layouts/people.aspx?MembershipGroupId=0&FilterField1=ContentType&FilterValue1=Person

Here's a quick reusable way to hide the left navigation.  Create a text file called "HideLeftNav.txt" in a document library.  Add the following css code: <style type="text/css"> /*--Hide Quick Launch --*/ #s4-leftpanel{ display:none } .s4-ca{ margin-left:0px } </style>    Edit the page you want to hide the nav on, add a content editor webpart. Then, simply reference the url to the HideLeftNav.txt file and you are done.  

 Find and make a backup copy of the Core.JS file(14templatelayoutsinc) Edit the Core.JS file(14templatelayoutsinc) Find the function called ErrorVisualization_ShowShortMessage Add "return;" as the first command in the function.ErrorVisualization_ShowShortMessage(b,a,g){return;ULSrLq:;var h=g[2],d="",e=null;if(!  Reset IIS  http://sharepointfeaturesandfailures.blogspot.com/2008/03/turn-off-hover-over-screen-tips-on.html

Here's a kind of fun web part I found on Codeplex. You can jump on the tiles bandwagon in SharePoint 2010. It's packaged nicely in 2 wsp files and creates a list to hold the data. Built in images are very nice. It's called the Metro Grid webpart and they have done a nice job on the packaging and icons. http://spmetrogrid.codeplex.com/