Tuesday, April 24, 2007

Fun with Explorer Toolbar development.

When the component is built and registered Explorer seems to be caching the component somewhere and does not replace the component despite the previous version being unregistered.

The only way I've been able to get around this is to manually kill the running "explorer.exe" process and restart a new Explorer session.

After building the Explorer bar project, bring up the Windows Task Manager using the Ctrl+Shift+Esc chord. Then under the Processes tab find "explorer.exe", right click and select "End Process". Your running VS.Net process should not be affected, but your taskbar will noticeably disappear. To resurrect Explorer, use the Alt+F, N chord to bring up the New Task dialog. Simply enter "explorer", without the quotes, then click OK. Your taskbar will reappear and your Explorer bar should be using the correct version.

I like to think that there is a better way to do this.

"A good plan executed today is better than a perfect plan executed at some indefinite point in the future."

- General George Patton Jr

Submit this story to DotNetKicks

1 comments:

Toolbar Development said...

Hey, it's great tips to repair explorer.