Yesterday I noticed that my list of tools to use in Visual Studio was more or less reduced to none. This concerned me since SSIS packages are all tools based and well, I can’t really do much if I can only run a backup database task.
After googling it for a bit, I found the post that explained exactly what to do. The cached toolbox files were screwed up and needed to be regenerated. I started by right clicking and saying “Reset Toolbox” but no luck.
In the end I had to kill all of the tbd files that were created automatically by Visual Studio (more information).
The paths in that post are for Vista and XP, so I found another one that actually defined where to find them in Windows 7 (Visual Studio Application Data Folder).
Make sure to close Visual Studio before trying this or who knows what will happen …
Hope this helps!
Today I was playing with Visual Studio 2008 and I went to run my application in debugging mode. After running it, I realized that there was a small issue that I wanted to resolve but I didn’t want to terminate the Web Application fully (i.e. just modify the code and then recompile). When I started typing, I got a nice little slap in the face from Visual Studio as seen below:
Debugging Error Message
After some hunting around on Google I came across a bunch of Stack Overflow posts that told me how to allow me to disable that nice little slap in the face in order to allow me to continue to code. To do this you must do the following (while the application is not running in debug mode):
- Click on “Tools”
- Click on “Options”
- Select “Debugging”
- Click on “Edit and Continue”
- Uncheck the “Enable Edit and Continue”
Disabling Edit and Continue
After following those steps I was good to go.