tags:

views:

139

answers:

2

So I'm writing a snapin for MMC 3. Quite often I have the debugger attached and I'm stepping through some code. MMC has some kind of a fail safe for misbehaving snapins that automatically unloads them after a timeout. The message is 'This snap-in is not responding'. After that MMC can behave as though your snap-in has been unloaded.

fair enough, it's not responding because I'm stepping through the debugger. However, the timeout is very small for development.

Does anyone know of a way of increasing the timeout? I googled and couldn't find anything. Checking the MMC registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC and couldn't see anything there. I also checked the snap-in registry location under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MMC\SnapIns. No luck.

I feel like there must be a way of increasing the timeout as this is something the devs as Microsoft must have encountered this problem.

A: 

Did you ever find a solution? I'm currently doing the same thing also ... I thought it was just a debug problem but when I ran the program out of debug it performed the same way everyonce in a while it would just crash. does you problem look like this?

(well i couldn't post and image because this was my first post on here but here is a link to the pic):

ScreenShot of Error

it looks very similar in windows 7 also I have installed and ran into this error in both xp and win7. I would be curious to know if this is the same error you are getting and would like to know if you found any solutions. I will also post this on MSDN to see what they have to say if I find anything out I will let you know.

Joe
I don't think my symptoms are quite the same as yours. When I run in debug but without the debugger attached everything runs fine.If you have a blocking (synchronous) piece of code that takes a long time you might get the symptoms that you're seeing. Make sure you're pushing all non gui work to background threads.
Ed Sykes
A: 

Thanks for the response I have solved this issue I was making a couple of stupid errors that I have since resolved. Thanks good luck 2 you

Joe