What to do when Visual Studio 2008 Debugger Kills Dreamweaver?

Visual Studio 2008 Debugger Kills Dreamweaver

Quoted “I’m not sure what caused the problem, but I know what fixed it. I ended up repairing Dreamweaver CS3, which the suite made pretty easy to do. I was going to uninstall DW and reinstall, but I tried the repair option first and sure enough, that fixed it. I still have no idea  what caused it to begin with.”

I have just encountered this problem with ‘unhandled win32 exception error in Dreamweaver.exe’ and VS2008 Debugger killing the application. I found that neither repairing/reinstalling Dreamweaver nor disabling debugging within IE fixed the problem. What has fixed the problem however is that the error was within a particular batch of files rather than with the actual application. I restored a last known good file batch from backup and everything returned to normal. It was only two corrupt files (html and css) that I was working on when the problem arose, that was causing me all the problems.

This worked for me:

If Dreamweaver is open, quit the application. Delete the WinFileCache-AD76BB20.dat file from the Dreamweaver user configuration folder. Note that on Windows, the Application Data and AppData folders are hidden by default, so verify that your Windows Explorer folder options are set to View Hidden Folders. The location of this file is as follows: Dreamweaver CS3 on Windows Vista:

C:\Users\{Yourusername}\AppData\Roaming\Adobe\Dreamweaver 9\Configuration

Dreamweaver CS3 on Windows XP:

C:\Documents and Settings\{Yourusername}\Application Data\Adobe\Dreamweaver\Configuration

Restart Dreamweaver.

Hope my article helps someone.