2 years.. and counting!

Yes, today I finish 2 years working with my Dream company! Its been great journey so far, and I guess company has given me everything that I ever dreamed for (except night job, but efforts are in motion to find some resolution to that! ) On development side, If I retrospect, I find that I…


Look at the operating system version and SP details from the dump in WinDbg..

This is a very common question, we encounter almost all the times. Just imagine a situation, we have got a memory dump from somewhere and want to see what operating system which is run there and what SP is installed.. For this, there is a very simple command. 0:001>vertarget Windows Server 2003 Version 3790 (Service…


How to change value of register when doing live debugging with Windbg?

Windbg has not only registers reading functionality but it can also modify registers when doing live debugging.. Its really useful sometimes to modify the register values and take different path to check for particular code branch.. You can modify the register value like this.. 0:000>r @eax=0x80040005 Above command will modify value of register eax and…


Collection of SysInternal Tools

The team has just released a new subdomain that has neat and clean list of all SysInternal Tools, ready for you!! Take a look, http://live.sysinternals.com Stay tuned..


Visual Studio 2008 SP1 Beta is available!!

I’ve been using Visual Studio 2008 from few months.. Its really a great improvement over productivity.. I love new features and speedy IDE. Service Pack 1 for Visual Studio 2008 contains not only bug fixes but also lots of new features! Along with .NET Framework 3.5 SP1 beta, VS2008 SP1 beta has been released few…


What is better way of keeping an eye on last win32 error while debugging?

I have found it necessary many times to keep an eye on last win32 error, while using Win32 APIs in code! (Calling GetLastError() after each API usage is not feasible solution!).. In Visual Studio they have provided a very good small feature. You can write @err,hr in the watch window, Similarly, you can use another…


How can I check the details about Process Token while debugging in Visual Studio?

Visual Studio 2005 onwards, watch window has got a pseudo register for investigating the details about process token. So, all you have to do is, just start debugging and write "$user" in watch window, Its interesting to look at expanded view of privileges and groups sometimes! Stay tuned..


CoCreateInstance returns 0x80080005 for Visual Studio 2008 based ATL service??

I just worked with a customer who was facing interesting issue. He was getting 0x80080005 at client when he calls CoCreateInstance. The COM component is implemented within an ATL Service which is running on the same machine (we are not hitting wire/network). Now, typical meaning of this error is, CO_E_SERVER_EXEC_FAILURE                                      winerror.h Server execution failed Generally…


VC++ Debug C++ Runtime Files..

How many times have you tried to run the debug build of your project on a test machine where you don’t have Visual Studio installed, and faced issues? Issues like, For binaries built in debug configuration with Visual Studio 2005.. Activation context generation failed for "<your file>". Dependent Assembly Microsoft.VC80.DebugCRT,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="8.0.50727.762" could not be found. For…


COM Interop Sample : Using C# DLL from C++ application

I have found many people who are beginning to learn COM Interop, looking for a sample application that explains how to use C# DLL from C++ application. Here is one sample that I developed (SLN file is in VS2008 format!) Stay tuned..