Some useful tools for windows development

http://www.hanselman.com/blog/ScottHanselmans2014UltimateDeveloperAndPowerUsersToolListForWindows.aspx

SharePoint 2013 Virtual Machine download

This is a preconfigured sharepoint 2013 virtual machine available for development evaluation

http://gauravmahajan.net/2013/01/06/sharepoint-2013-rtm-on-win-server-2012-virtual-machine-download/

http://www.cloudshare.com/showcase

https://drive.google.com/folderview?id=0Bx2qIP65NZrJUjlMNWhndXctQkk&usp=sharing#list

Create a SharePoint 2013 app

The posts below explain how to create basic and advanced apps in SharePoint 2013. These apps access SharePoint object model through Client object model or through rest web services or OData model. Thus our code is lot more safe and secure, it can be easily managed and the application as a whole is a lot more flexible. Please note that the basic .Net framework version used is 4.5.

http://msdn.microsoft.com/en-us/library/office/fp142379(v=office.15).aspx

http://www.codeproject.com/Articles/690015/SharePoint-Online-App-Development-Part

http://sharepoint.stackexchange.com/questions/54008/how-to-create-apps-for-sharepoint-2013-in-visual-studio-2012


In SharePoint 2013 development can be done either in "Napa" web development platform or visual studio of SharePoint designer.

SharePoint 2013 Identity Model and claims aware apps

The new SharePoint 2013 Identity authentication model has lot of cool features, however configuring it the right way is absolute essential for our apps to be able to use it, here are some links which throw more light on that aspect

http://technet.microsoft.com/en-us/library/jj715264(v=office.15).aspx

http://www.harbar.net/articles/fimportal.aspx

http://thesharepointfarm.com/2013/06/using-an-external-identity-manager-for-sharepoint-user-profile-synchronization/

Sharepoint cache.ini access denied permission issue

This post helps in some cases
http://dizzyonsharepoint.wordpress.com/2011/10/28/sharepoint-caching-access-denied/


This post handles the problem with lock hunter program

http://www.codeovereasy.com/2012/12/locked-file-in-sharepoint-configuration-cache/

Also this post has very useful information

http://smcroy.wordpress.com/2010/10/17/security-changes-required-for-sharepoint-timer-job/

Visual studio remote debugging symbol files location

Visual studio has a great facility to do remote debugging which is a lifesaver in many cases where our code works at one location but then fails to run properly at some other location. However, we need to be careful while using the remote debugger components. I have listed the major points to consider below:

1. There are two separate debugging tools for x86 and x64 environmets
2. Remote debugger on the remote machine needs to be run with the same user account as the user account used to run visual studio on development machine. (There is an option to relax permission settings and allow any user to debug, but when I tried to use it, it didn't work for some reason.)
3. Debug symbol files (.pdb) location is very important, since visual studio has to be able to locate these files on local as well as the remote machine. The rule of thumb in this case is to place them at the same relative location on both development machine and the remote machine. A detailed explanation can be found in this post http://www.wintellect.com/blogs/jrobbins/visual-studio-remote-debugging-and-pdb-files