Stack Overflow profiler open sourced: Profiling your website like a true Ninja.
Smaller is Faster (and Safer Too). Chrome team have just started using a new compression algorithm called Courgette to make Google Chrome updates small. Read more.
Ask Amir Taaki About Bitcoin. From Slashdot.
The Four Stages of NTFS File Growth from Windows Server Core Team.
Some articles from CodeProject:
Rosa Golijan writes about what happens on the Internet every 60 seconds.
The Biggest Changes in C++11 (and Why You Should Care) by Danny Kalev.
Are You Too Good For Code Reviews? Articles and discussion in Slashdot.
Google’s Swiffy converts Flash SWF files to HTML5.
Have you wondered whether WordPress can handle high-volume traffic? High Traffic Tips For WordPress.
The most detailed story about Stuxnet: How Digital Detectives Deciphered Stuxnet, the Most Menacing Malware in History.
How to build your own 135TB RAID6 storage pod for $7,384 from extremetech.com.
Investigation: Is Your SSD More Reliable Than A Hard Drive? from tomshardware.com.
pdf.js is a technology demonstrator prototype to explore whether the HTML5 platform is complete enough to faithfully and efficiently render the ISO 32000-1:2008 Portable Document Format (PDF) without native code assistance. From Dr. Andreas Gal.
Today I tried to figure out why one of my Visual Studio Projects failed to embed a Manifest. I had Generate Manifest and Embed Manifest enabled under Linker / Manifest tool, but manifest was not embedded.
Long story short, after 2 hours of configuring, rebuilding, creating, deleting, I had the following state:
– Move project to C: drive, and Linker embeds manifest as expected.
– Move project to D: drive, and manifest is not embedded into exe file.
– Move project to D: drive, and add a dummy resource, and Linker embeds manifest as expected.
– Bonus to all this, Release version worked like a charm, but Debug version did not.
Looking at disk properties revealed, that C: is NTFS drive, but D: is my old FAT32 drive. Then I recalled, that there was one strange option in Visual Studio 2008 Manifest Tool, called ‘Use FAT32 Work-around’. From MSDN documentation:
FAT and FAT32 file systems have up to a two second latency between the time that a file is changed and the time that the file's time stamp is updated. This latency prevents the build process from determining whether or not relevant files are up-to-date.
Yes introduces a two second delay to allow the manifest tool (Mt.exe) to properly embed the manifest on FAT and FAT32 file systems. If you are building a project on a FAT or FAT32 file system, select Yes.
Use FAT32 Work-around in Visual Studio 2008:
The problem is, that if you open the same properties in Visual Studio 2010, then there is no such option anymore. Option ‘Use FAT32 Work-around’ is removed from Visual Studio 2010. It means that Visual Studio 2010 works only on NTFS. This is not mentioned in System Requirements, but who is using FAT32 anyway?
So currently my workaround is to convert my old drive to NTFS.
Beginning from Windows Vista and Windows Server 2008 it is possible to encrypt Windows paging file. Paging file can contain your credentials, passwords, session data, temporary data from database, etc.
To check if encryption is enabled use the following command in cmd window:
fsutil behavior query encryptpagingfile
To enable encryption:
fsutil behavior set encryptpagingfile 1
P.S. After enabling, your system may work a little bit slower, but normally you won’t notice it.
P.S.S. This works only on NTFS and will not work on FAT32.
Also, encrypt the Temp folder on your hard disk to ensure that your encrypted documents remain encrypted during editing.