"How many of you skip source control for certain apps? "

To be painfully honest, I do skip source control for some things.

For anything to goes into production or pseudo-production I use source control. For most of the heavy research I do, I also use a private source control library setup especially for me. For some quick and dirty stuff I write on this PC just to see if I can bend something construct to do something it is not really intended to do for curiosity sake, I may or may not keep it in source control, that depends on the outcome and the amount of effort required.

But there are throwaway pieces of code that I write in a stand-alone project that will be cloned or cut and pasted into another project. This is transitional stuff that does not have a long shelf-life and gets tossed in a few hours. Those are tossed before they ever see source control.

But most stuff that does not see source control are exceptions to the rule. Often now I will build a C# solution that have multiple projects in it, one being the production or candidate production code, any number of research projects, there also could be a few dlls, web services, and other objects like test harnesses of custom server side controls or the web services I develop. That all sees source control.

Summary - As a rule almost everything gets to source control, and I have a huge library of classes and objects I use to build new things with. I have to have that stuff under source control. And I find that I wonder more why I saved some pieces of code instead of wondering why I did not save something.