This is a couple of solutions to the windows XP search bug.

I call it a bug, MS calls it a feature.  If windows does not recognize the file extension it will be excluded from searches.

This cost businesses money in pointless searches for files that really do exist but claim not to.

It the banking world it is common to have transfer files with a sequential number extension (possibly a serialized date).

Trying to prove that your app is not skipping messages is far more difficult than it needs to be.

This and This are articles about using K2 with MSBuild.

This is something that I am going to have to do soon as we need to deploy our code to production via K2.

Here is a great article on using the ASP.Net cache outside of web apps.

This is the gist of the article:

• Add System.Web to your references
• Get the actual cache object using

private Cache m_Cache;

m_Cache = HttpRuntime.Cache;

I have a colleague to thank for this:

This is blisteringly fast and just works.

use Core

go

checkpoint

go

backup log “Core” with truncate_only

go

DBCC SHRINKFILE ( “Core_log” )

go

use OtherDB

go

checkpoint

go

backup log “OtherDB” with truncate_only

go

DBCC SHRINKFILE ( “OtherDB_log” )

go